Skip to content

Conversation

@drobnikj
Copy link
Member

No description provided.

@github-actions github-actions bot added this to the 115th sprint - Platform Team milestone May 19, 2025
@github-actions github-actions bot added the t-core-services Issues with this label are in the ownership of the core services team. label May 19, 2025
@apify-service-account
Copy link

Preview for this PR was built for commit e40452f and is ready at https://pr-1591.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit e97cd8d9 and is ready at https://pr-1591.preview.docs.apify.com!

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
Copy link
Contributor

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?

Copy link
Member Author

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

in: query
description: |
A unique identifier of the client accessing the request queue. It must
be a string between 1 and 32 characters long
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

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 😄

Copy link
Contributor

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.
Copy link
Contributor

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)?

Copy link
Member Author

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the description.

@drobnikj drobnikj requested a review from janbuchar May 20, 2025 15:16
@apify-service-account
Copy link

Preview for this PR was built for commit 2088cab4 and is ready at https://pr-1591.preview.docs.apify.com!

@apify-service-account
Copy link

Preview for this PR was built for commit 4658525c and is ready at https://pr-1591.preview.docs.apify.com!

@drobnikj drobnikj added the adhoc Ad-hoc unplanned task added during the sprint. label May 26, 2025
@janbuchar janbuchar merged commit 7f28477 into master May 26, 2025
9 of 10 checks passed
@janbuchar janbuchar deleted the feat/api-rq-unlocking branch May 26, 2025 09:48
@fnesveda fnesveda added the validated Issues that are resolved and their solutions fulfill the acceptance criteria. label May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint. t-core-services Issues with this label are in the ownership of the core services team. validated Issues that are resolved and their solutions fulfill the acceptance criteria.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants