chore(deps): lock robosystems-client 1.13.1 - #10
Merged
Merged
Conversation
1.13.1 replays a rate-limited request instead of surfacing the 429. The rejection is raised before the endpoint handler runs, so the call had no effect and the replay is safe. This covers `demo_loop`'s own client use (provisioning, teardown, API keys). The episode load that actually hit the rate limit runs from the robosystems checkout and takes its SDK from *that* repo's lockfile, so this alone does not fix the failing run — RoboFinSystems/robosystems#1318 is the half that does. Lock only: the `>=1,<2` floor stays where it is.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pulls through
robosystems-client1.13.1, which replays a rate-limited request instead of surfacing the 429 (RoboFinSystems/robosystems-python-client#201). The rejection is raised by a request dependency before the endpoint handler runs, so the call had no effect and the replay is safe even for aPOSTwith no idempotency key.This covers
demo_loop's own client use — graph provisioning, teardown, API keys.This alone does not fix the failing demo run. The episode load that hit the rate limit runs from the robosystems checkout and takes its SDK from that repo's lockfile, not this one — RoboFinSystems/robosystems#1318 is the half that does, and it also stops the runner from swallowing dropped events into a counter.
Changes
uv.lock—robosystems-client1.12.0 → 1.13.1. Lock only; the>=1,<2floor stays where it is.Testing
ruff check,ruff format --check,basedpyrightclean;pytest6 passed.