When MRW scan returns a negative pong, abort don't assert #75
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
ecpeterson
approved these changes
Jun 23, 2025
| @@ -125,12 +125,22 @@ After collecting the `HOLD-CLUSTER', we then `CHECK-PRIORITY' to determine if we | |||
| :message-unpacker identity) | |||
| (send-message-batch #'payload-constructor roots) | |||
| (loop :for reply :in replies :unless (null reply) | |||
| :do (assert (not (minusp (message-pong-weight reply)))) | |||
There was a problem hiding this comment.
true, we could be stale at any moment, including this one.
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.
The standard supervisor reaction to a negative pong is to CHECK-PONG it. We could do that instead here, but aborting is also fine as long as the pong is truly based off of stale information.
Also does some logging work related to dtqec/aether#49