Repository navigation
Finish reorg recovery without per-launch pool request bursts - #57
Merged
Merged
Conversation
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.
Recovery rechecked every historical refunded launch with a separate pool lookup. Production repeatedly hit Counterparty's rate limit before its final block check, leaving recovery unfinished even after the graduate and graveyard rows were restored.
Read the complete pool listing once during recovery, follow every cursor, and use that snapshot for all closed launches. Failed pages, malformed responses, and repeated cursors leave pool status unknown and preserve existing phases/reserves; ordinary indexing keeps its existing incremental behavior.
Validation:
npm run checkpassed (1,452 tests, 17 render-read checks, type/lint/numeric/i18n checks). Regression covers 208 refunded launches, a failed snapshot followed by successful recovery, preserved graduate reserves, cleared recovery markers, and a single pool-list request. Pagination tests cover later-page pools and incomplete listings.