fix: when deciding if we need to propagate a reply, skip branches scheduled for cancellation but with no replies yet #3687
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
…d for cancellation but with no replies yet
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.
Summary
Current bug is :
The bug is that the 486 does not get propagated on the spot - it gets saved internally and relayed only when fr_timeout elapses.
Details
Ignore branches scheduled for CANCELation via t_cancel_branch, which don't have any replies on them yet.
Solution
Ignore branches scheduled for CANCELation via t_cancel_branch, which don't have any replies on them yet.
Compatibility
Should be backwards compatible - I hope.