Upstream iroh 1.1.0 / noq 1.2.0; experiments on released noq and the lannbot forks - #104
Merged
Conversation
…d the lannbot forks Main workspace: noq-proto =1.2.0 (the endpoint's QUIC core), iroh =1.1.0 (the interop peer) and the co-pinned iroh-relay 1.1.0 binary. No API adaptation was needed. Upstream changes with a bearing on this endpoint: - noq#771: the per-path idle timer is armed only once multipath is negotiated. This endpoint never negotiates multipath, so upstream peers used to run a 15s path-idle clock against us that the protocol never agreed to; keep-alives masked it. - noq#782: a coalesced datagram tail for an unknown path no longer panics the decoder. - iroh#4473: upstream stops sending the endpoint ID as SNI. This endpoint already sent a fixed placeholder and never read SNI server-side. - iroh#4455: a new relay Status variant (RateLimited), no protocol version bump; this client ignores Status frames. - iroh#4465: the serialized CustomAddr form changed. Nothing here parses upstream address records yet. Experiments: noq#773 (wasip2 support in noq-udp) is released in 1.2.0, so the noq git patches go. The remaining wasi patches (lann/iroh#1-3, lann/net-tools#1-2) are rebased onto v1.1.0 and netwatch-v0.19.3 on the lannbot/iroh and lannbot/net-tools forks, pinned by rev. All three guests build; the relay-ws spike runs end to end (relay bootstrap, migration onto the data channel).
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.
Main workspace
noq-proto=1.1.0→=1.2.0(endpoint),iroh=1.0.3→=1.1.0(tools/iroh-peer),IROH_RELAY_VERSION1.0.3 → 1.1.0 (scripts/setup.sh), plus the version citations inendpoint_impl.rsdoc comments (the cited constants —CONNECT_TIMEOUT,PING_INTERVAL,PING_TIMEOUT— are unchanged at 1.1.0) and the README interop claim.rustlsstays at 0.23.43. The wasm component's dependency graph changes by exactly one crate.Upstream changes with a bearing on this endpoint:
core/src/tls.rs) and never read SNI server-side; interop unaffected either direction.Status::RateLimited, no protocol version bump;recv_datagramignoresStatusframes.CustomAddrserialization changed (marked breaking). Inert: nothing here parses upstream address records yet. Relevant when discovery lands.Experiments
noq#773 (wasip2 support in
noq-udp) is released in 1.2.0, so the three guests' noq[patch.crates-io]git pins are deleted. The remaining wasi patches (lann/iroh#1–3, lann/net-tools#1–2) are rebased onto v1.1.0 and netwatch-v0.19.3 (which iroh 1.1.0 requires) on thelannbot/irohandlannbot/net-toolsforks, branchpolymorph-iroh, pinned by rev. The net-toolsposix_minimalpatch was re-targeted at 0.19.3's newnetdevcfg alias as its own commit message anticipated; the iroh patches applied clean.Same ruling everywhere it holds (noq family → released 1.2.0), three near-identical diffs.
Gates
just check,just build,just matrix(13/13 pairings, incl. both UDP interop directions against the 1.1.0 peer and relay) — pass.cargo build --releasein all three experiment guests — pass.just iroh-relay-ws— runs end to end on the rebased stack: relay bootstrap, migration onto the data channel, echo RTT drop. The fourrelay_recv_channel closedteardown log lines are pre-existing (verified against the previous configuration).Automerge is armed.