Repository navigation
Treat an event no relay accepted as a failed send - #1001
Merged
Merged
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 36 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Client::send_eventin nostr-relay-pool 0.44 returnsOkeven when every relay refused the event; the refusals are only listed in the returned output. The FROST transport, the DKG transport andfrost network group-createignored that output, so a refused event counted as sent:group-create --publishreported the roster as published when no relay stored it, and signing or DKG rounds later timed out without saying why.All three now fail when no relay accepted the event, naming each relay's reason.
Where a refused send must not end the operation:
run()is logged and left to the periodic re-announce; other failures, such as a TPM quote, still stop the node.Tests: a unit test covers accepted, partly refused and fully refused sends. The in-memory test transport can now refuse matching events: a DKG whose first send of each round is refused completes (it timed out before), a node whose first announce is refused keeps running, and a 3-of-3 round signs when one cosigner's share to another is refused. The first two fail without their fix; the signing test depends on peer order and failed in 4 of 6 runs without it. keep-frost-net and keep-cli tests pass, and both real-relay multinode tests (signing, and learning followed by interactive signing) pass against a public relay, so relays acknowledge the ephemeral protocol events as before.