Upgrade deps: noq-proto 1.2.0, wasmtime 48, compatible bumps - #53
Merged
Conversation
cargo update takes noq-proto 1.1.1 -> 1.2.0 (congestion/pacing/idle-timer internals; the crypto seam and the Endpoint/Connection API this repo uses are unchanged) plus the compatible bumps across the graph. rust/tls-virt-wasmtime moves to wasmtime 48. wasmtime-wasi 48 denies TCP socket creation unless allow_tcp is set, gives p2 its own TcpSocket wrapper with re-shaped HostTcpSocket/HostUdpSocket signatures, and removes the public Network::check_socket_addr. The 0.2 tunnel path therefore now bypasses the sandbox address check like the 0.3 path; the README and module docs say so. wasip3/wit-bindgen stay at 0.7/0.60: polymorph-test is on wit-bindgen 0.60, and guest-ct must share its line.
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
2 participants
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.
What
cargo update: ~110 compatible bumps, including noq-proto 1.1.1 → 1.2.0. The 1.2.0 code changes are congestion (BBRv3 sync from quinn), pacing, per-path idle-timer fix, and a coalesced-datagram-on-unknown-path panic fix;crypto/mod.rs(the trait surfacerust/quicimplements), the rustls glue, and theEndpoint/ConnectionAPI the drivers use are untouched (the remaining diff is a comment-reflow rustfmt pass).rust/tls-virt-wasmtime:wasmtime-wasi48 denies TCP/UDP socket creation by default (Disallow TCP/UDP socket creation by default bytecodealliance/wasmtime#13936);inherit_network()no longer implies it, so the builder now setsallow_tcp(true).TcpSocketwrapper;HostTcpSocket::start_connectbecame sync andstart_listenasync, p3HostUdpSocket::createbecame async. The delegating impls follow.Network::check_socket_addris gone with no public replacement (SocketAddrCheckispub(crate)), so the 0.2 tunnel path now bypasses the sandbox address check exactly like the 0.3 path. README and module docs updated; issue Productionize the tls-virt deliveries #16 already tracks the address-policy gap.wasip30.7 /wit-bindgen0.60 + the two 0.57 pins.wasip30.8 is the same WIT on wit-bindgen 0.61, butpolymorph-test(0.2.1 and the new 0.3.0) is on 0.60 andconformance/guest-ctmust share its line, so the bump would only move the split, not remove it.Gates
just check,just smoke-tls-virt(all four legs),just smoke-quic,just interop(TLS both directions incl. close_notify/truncation/reset, QUIC both directions vs quic-go) — all green locally.Automerge armed.