You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior. How do you call the dredd command? Which command line options?
Expected behavior
A clear and concise description of what you expected to happen.
We're using dredd to use the dredd.yml spec to perform an order of requests:
Adding a show
Getting resources for a show
Other actions we want to do on a show
Delete show
Only issue is that the application will add the show threaded. Meaning it will provide a queue item id back as response. And then start adding the show.
The followup requests will asume the show has been added to the db. But it hasn't.
Is there are way to build in a delay, to make sure the show has been added at that point.
Nicer solution would be the ability to loop a different requests for a max of time, to check if the show has been added. In our frontend we utilize the queue item id for that.
What is in your dredd.yml?
Order of requests for:
Adding a show
Getting resources for a show
Other actions we want to do on a show
Delete show
/series:
post:
summary: Add seriesdescription: | Given an indexer and its id, adds the series to Medusa.parameters:
- name: seriesin: bodyrequired: truedescription: Only id (with indexer information) should be specifiedschema:
example:
id:
tvdb: 301824responses:
201:
description: Series addedheaders:
Location:
type: stringdescription: The location of the newly added seriesschema:
$ref: '#/definitions/SeriesQueueItem'400:
$ref: '#/responses/error'description: Invalid requestx-request:
body: {}404:
$ref: '#/responses/error'description: Series not found in the indexerx-request:
body:
id:
tvdb: 99999999409:
$ref: '#/responses/error'description: Series already addedget:
summary: Return series that the user has access todescription: | The Series endpoint returns information about the Series added to Medusa.parameters:
- name: pausedin: queryrequired: falsedescription: Filter series based on paused statustype: boolean
- $ref: '#/parameters/detailed'
- $ref: '#/parameters/episodes'
- $ref: '#/parameters/page'
- $ref: '#/parameters/limit'
- $ref: '#/parameters/sort'responses:
200:
$ref: '#/responses/pagination'description: A paged array of seriesschema:
type: arrayitems:
$ref: '#/definitions/Series'400:
$ref: '#/responses/error'description: Invalid pagination parametersx-request:
query-params:
sort: abc/series/{id}:
get:
summary: Return information about a specific seriesdescription: Retrieves information about a specific seriesparameters:
- $ref: '#/parameters/series-id'name: id
- $ref: '#/parameters/detailed'
- $ref: '#/parameters/episodes'responses:
200:
description: The series informationschema:
$ref: '#/definitions/Series'400:
$ref: '#/responses/error'description: Invalid idx-request:
path-params:
id: 123456404:
$ref: '#/responses/error'description: Series not foundx-request:
path-params:
id: tvdb999999999patch:
summary: Partial update seriesdescription: Partial update seriesparameters:
- $ref: '#/parameters/series-id'name: id
- name: seriesin: bodyrequired: falsedescription: Currently, only pause field is supportedschema:
$ref: '#/definitions/Series'responses:
200:
description: Response with only the updated fieldsschema:
$ref: '#/definitions/Series'x-request:
body:
{"tvdb": 301824, "paused": true}400:
$ref: '#/responses/error'description: Conflicting series identifierx-request:
body:
id:
tvdb: 80379path-params:
id: tvdb301824404:
$ref: '#/responses/error'description: Series not foundx-request:
body:
id:
tvdb: 999999999path-params:
id: tvdb999999999delete:
summary: Delete a seriesdescription: Delete a seriesparameters:
- $ref: '#/parameters/series-id'name: id
- name: remove-filesin: queryrequired: falsedescription: Whether files from the series should be removedtype: booleanresponses:
204:
description: Series is deleted successfully400:
$ref: '#/responses/error'description: Invalid idx-request:
path-params:
id: 123456404:
$ref: '#/responses/error'description: Series not foundx-request:
path-params:
id: tvdb999999999409:
$ref: '#/responses/error'description: Unable to delete series
What's your dredd --version output?
dredd v13.1.2 (Windows_NT 10.0.18363; x64)
Does dredd --loglevel=debug uncover something?
If you run Dredd with debugging output, do you see any interesting information relevant to the bug?
We changed from adding shows sync to async.
After the change, we noticed subsequent requests where failing.
Can you send us failing test in a Pull Request?
We'll gladly help you to contribute; answering yes raises the chances the issue gets fixed.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior. How do you call the dredd command? Which command line options?
Expected behavior
A clear and concise description of what you expected to happen.
We're using dredd to use the dredd.yml spec to perform an order of requests:
Only issue is that the application will add the show threaded. Meaning it will provide a queue item id back as response. And then start adding the show.
The followup requests will asume the show has been added to the db. But it hasn't.
Is there are way to build in a delay, to make sure the show has been added at that point.
Nicer solution would be the ability to loop a different requests for a max of time, to check if the show has been added. In our frontend we utilize the queue item id for that.
What is in your
dredd.yml
?Order of requests for:
What's your
dredd --version
output?Does
dredd --loglevel=debug
uncover something?If you run Dredd with debugging output, do you see any interesting information relevant to the bug?
We changed from adding shows sync to async.
After the change, we noticed subsequent requests where failing.
Can you send us failing test in a Pull Request?
We'll gladly help you to contribute; answering yes raises the chances the issue gets fixed.
The text was updated successfully, but these errors were encountered: