You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your s
8000
ession.Dismiss alert
{{ message }}
Repository navigation
On a native host, a box whose switch does not start publishes its name with no declared forward bound #3716
On a native Linux host, when the network switch does not start, the box's finalize logs a warning and publishes the box's name with no declared ingress forward bound. Design §7.1 line 255 requires the forwards to be bound before the name is published, and the VM-backed arm already fails the finalize in that case.
The finalize cannot fail there yet, because every own-IP finalize in the minimald test suite would then need a switch. TestServer in crates/minimald/src/test_harness.rs has no switch stand-in.
Done when
TestServer provides a default switch stand-in for own-IP boxes.
The Some(Err) arm of the native finalize returns the error, so a switch that does not start fails the finalize with its reason, and the name is not published.
host_ports_in_use in crates/minimald/src/box_actor/setup.rs is retired.
Activity
docs(minimald): cite #3716 for the native switch-not-started case
fix(minimald): a native Linux host binds a box's declared ingress for…