Repository navigation
Conversation
… for the rate limit Co-authored-by: claude-code/anthropic/sonnet-5-5 <claude-code@agents.peck.to>
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
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.
Refs #6 (part 1) and #7 (part 1). Does not close them: restart/multi-instance UTXO state (#6) and the dependency alerts (#7) are not addressed here, and #5 is a decision for the owner.
What:
SponsorWallet.buildSubmitAndAdvanceholds the lock across build, overlay submit and UTXO advance, so concurrent/postcalls chain off each other instead of building from the same UTXO.PostControlleruses it; error mapping (402/503/502) is unchanged.app.set("trust proxy", 1)so the 10/min/postrate limit is keyed per client (Cloud Run adds one hop) instead of one shared bucket.How tested: two new tests (concurrent posts chain; per-client rate-limit key). Both fail on master and pass here;
npx jest32 passed,tsc --noEmitclean.[HOLD]: live service with a funded mainnet key; no build trigger, so merging deploys nothing. If the service is kept, deploy by hand after the decision in #5.