-
Notifications
You must be signed in to change notification settings - Fork 23
feat(node,config,network-libp2p): per-worker network swarms (#555, PR 2) #1315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
49ab230
feat(node,config,network-libp2p): per-worker network swarms (#555, PR 2)
MavenRain e2bc1aa
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain c90fd0d
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain c8e133d
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain 9f62604
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain 0bea846
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain c53ab34
Merge remote-tracking branch 'origin/main' into 555-per-worker-networ…
MavenRain 1748aba
fix(network): isolate worker discovery and validate swarm config
MavenRain ebf7da6
test(network): persist Kademlia deletions before assertions
MavenRain 010bf9a
Merge main into 555-per-worker-network-swarms
MavenRain File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The derived Debug on KeyConfigInner renders the worker network seed, and this PR dropped the positive assertion that kept the worker side of the leak test honest.
KeyConfigInneris#[derive(Debug)](keys.rs:211) and now holdsworker_network_seed: Stringon this line.KeyConfigis#[derive(Debug, Clone)](:234) overArc<KeyConfigInner>, andArc'sDebugforwards to the inner value — soformat!("{:?}", key_config)does render the seed.This is informational rather than urgent, for two reasons. The seed is a domain-separation label, not key material: it's operator-configurable, read from
node_keys_path().join(WORKER_NETWORK_SEED_FILE)atkeys.rs:356-358. And no production log path debug-prints aKeyConfig— I grepped every tracing macro plusformat!,dbg!andprintln!and found zero sites.Still worth closing, since the type is one
?key_configaway from leaking, and the swap to a stored seed removed the only thing that would have caught a regression. A manualDebugforKeyConfigInnerrendering the seed as"<redacted>"handles the first part.For the second: the diff replaces the worker positive anchor in
debug_does_not_leak_key_materialwith a comment explaining that the worker side has no anchor now. That's true as written, but it leaves the worker half of the test with no assertion at all. A negative assertion would restore coverage and would fail if the seed ever starts rendering:That pins the redaction directly, rather than relying on the absence of a field that could come back.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the manual
Debugimplementation in 1748aba, rendering the stored seed as[REDACTED]. The leak test now explicitly rejects the seed and checks positive anchors for redaction and public fields.