-
Notifications
You must be signed in to change notification settings - Fork 135
feat: API: request queue unlocking docs #1591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
| A unique identifier of the client accessing the request queue. It must | ||
| be a string between 1 and 32 characters long | ||
| style: form | ||
| explode: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Um, it's just a simple string query parameter, why style: form and explode: true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly not sure, I just reused this param from the current rq endpoint see
apify-docs/apify-api/openapi/paths/request-queues/request-queues@{queueId}@[email protected]
Line 153 in d676859
| explode: true |
| in: query | ||
| description: | | ||
| A unique identifier of the client accessing the request queue. It must | ||
| be a string between 1 and 32 characters long |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd use minLength and maxLength instead (https://swagger.io/docs/specification/v3_0/data-models/data-types/#strings)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, let's move this in separate PR as I need to update it everywhere 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, are you up to it or shall I make an issue? 🙂
| - Storage/Request queues/Requests locks | ||
| summary: Unlock requests | ||
| description: | | ||
| Unlocks requests in the queue for the client. The requests are unlocked if were locked by the same client key or if locked from the same Actor run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand what this actually does. Does it unlock all requests locked from the same run, and (in addition to) all requests locked by the same client key (I assume to account for working with the RQ from a script outside of the platform)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if the client is within the Actor run it will unlock all request locked by this Actor run plus additionally all lock lock by the clientKey. If the client is outside if Actor run it will unlock just request locked by the same clientKey.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I updated the description.
|
Preview for this PR was built for commit |
|
Preview for this PR was built for commit |
No description provided.