Repository navigation
add repair-aware receiver sync policy - #114
Open
sleepybishop wants to merge 1 commit into
Open
sleepybishop wants to merge 1 commit into
sleepybishop wants to merge 1 commit into
Conversation
sleepybishop
marked this pull request as ready for review
August 29, 2026 17:40
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.
Hello,
Following up on the conversation in #113, this PR introduces a new synchronization policy,
NORM_SYNC_REPAIR. As discussed, this policy acts similarly toSYNC_CURRENTbut is more permissive, allowing a receiver to sync on parity/repair packets rather than exclusively on packets with user data content.SYNC_REPAIRpolicy toNormSenderNode::SyncPolicy.normNode.cppandnormObject.cppto properly track and allow syncing on repair messages.NORM_SYNC_REPAIRto the language bindings (C#, Java, Python, Rust).tests/normRepairFlagTest.cppto validate the newSYNC_REPAIRpolicy.I'd be happy to adjust the approach or just consolidate this logic into
SYNC_CURRENTif you think that's preferable for NORM.