chore(deps): lock robosystems-client 1.13.1 - #12
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 — which matters here, since a backfill looping the emit operations runs at the endpoint category budget and every rejection previously reached the caller as an ordinary failure. Lock only: the `>=1,<2` floor stays where it is, per the two-tier client contract. The emit surface is unchanged and still imports clean.
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).That 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 a
POSTwith no idempotency key. It matters for this template specifically: a backfill looping the emit operations runs at the endpoint category budget, and every rejection previously reached the caller as an ordinary failure. The demo tenant load that prompted the client fix lost 25 of 383 events that way.Changes
uv.lock—robosystems-client1.12.0 → 1.13.1. Lock only; the>=1,<2floor stays where it is, per the two-tier client contract.No source changes. The frozen emit surface (
AuthenticatedClient,UNSET, the six emit operations and their request models) is untouched by 1.13.1 and still imports clean.Testing
ruff check,ruff format --check,basedpyrightclean;pytest6 passed.src/integration/emit/imports against the new client.