Repository navigation
fix(dm): nodes advertise their DM address (v0.3.75) - #379
Merged
Merged
Conversation
Live on 0.3.74 every node created its DM identity (logged "node DM identity") but none advertised hardware.dm: the hardware blob is built once at boot, before secure chat starts, and the advertise loop re-sends that snapshot. with_instance (run each tick) now adds the address, so `c0mpute dm send <node>` can resolve nodes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan14 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
ralyodio
added a commit
that referenced
this pull request
Nov 15, 2026
…380) * test(hosting_market_e2e): give convergence CI headroom (90 s -> 240 s) preferred_hosts_hold_pass_challenges_and_get_paid failed on most master runs on 2026-11-15 (and on #371/#379): the first three copies land within seconds, but one host's 5 MiB fetch fails and retries ("chunks still missing"), the second preferred copy arrives ~60 s in, and the extra copies still need their trim grace, which ran past the 90 s wait on loaded runners. The test still requires both preferred hosts and exactly three stable copies; only the time allowed grows (agreement window 60 s -> 120 s too). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ci(rust): retry failed tests once by exact name Multi-node loopback E2Es time out now and then on loaded runners; on 2026-11-15 hosting_market_e2e, hosting_e2e, git_e2e and a private-objects replication test failed across most PRs and on master. The Test step now runs with --no-fail-fast, and only if it fails reruns each failed test once by exact name; a test that fails twice still fails the job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow-up to #374. Live on 0.3.74, every node created its DM identity (the worker logs
secure-chat: node DM identity … address=…), but no node advertisedhardware.dm, soc0mpute dm send <node>couldn't resolve any node. Cause: the supervisor builds the hardware blob once at boot (supervisor.rs:130), before secure chat starts, and the advertise loop re-sends that snapshot.with_instance, which runs on every tick, now adds the address.🤖 Generated with Claude Code