Repository navigation
[RUST-CI-031] Fix and prove client UDP v4 parity - #214
Merged
Merged
Conversation
added 7 commits
November 2, 2026 11:39
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.
Scope
These fixes were discovered by the bilateral deterministic parity campaign, not by log-string comparison.
Evidence
Receipt
rust-mfc-client-udp-v4-20261102t123752zproves Rust and MFC emitted byte-identical UDP v4 requestc5907a95c62c0a406c3fd822ed7de2429f8f0100000100and ACKc59100000100bytes in both directions and applied the same part status, complete-source count, and queue rank.Validation
20261102T122933Z-build-clients)938bce6cf18971e900cbb78a2c92f2dc585e1a3fThis is one bounded slice of #164 and does not claim the other eight client-UDP variants.