Repository navigation
Validate queued request ordering across reconnects - #5
Closed
LighthouseRobotics wants to merge 8 commits into
Closed
LighthouseRobotics wants to merge 8 commits into
LighthouseRobotics wants to merge 8 commits into
Conversation
…proof body Restore omitted authentication cookie proof body
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.
Queued client requests use decimal request IDs as map keys, so reconnects previously replayed
10before9. This branch orders active requests numerically, uses the same order for pending messages, removes acknowledged entries, and preserves the existing saved state and request bytes.This draft runs the repository CI in the contributor fork before submitting upstream. Focused regression validation passes on this head and reproduces the original ordering and queue-cleanup failures against the baseline client.