Repository navigation
fix(replay): bound verification memory and concurrent work - #9
Merged
Merged
Conversation
tee8z
marked this pull request as ready for review
October 9, 2026 12:49
This was referenced Oct 9, 2026
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.
Score verification now validates the frame count against the encoded log and decodes frames incrementally. Two submissions can hold verification permits at once; excess work receives a retryable HTTP 503. Blocking verification retains its permit through cancellation and checks a ten-second work budget. Normal replay physics and persisted input formats are unchanged.
The browser retries explicit busy responses using the original submission and offers a manual save retry if the service remains busy. It does not automatically retry ambiguous failures. Release 0.3.5 also makes the older ARM deployment workflow manual; tagged archives continue through the release workflow and the cluster's nix-rollout deployment.
Validation: all 72 Rust tests and three client submission tests passed; formatting and clippy passed. Regression tests cover invalid frame counts and lengths, odd frames, worker saturation/cancellation/failure, time-budget rejection, and preserved retry payloads. CI will also build both native architectures and WASM and run browser tests.