8000 On a native host, a box whose switch does not start publishes its name with no declared forward bound · Issue #3716 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

On a native host, a box whose switch does not start publishes its name with no declared forward bound #3716

Open

Description

@norrietaylor

Residual of #3703 (task #3646), arch condition C1 at 0062a4e.

Problem

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.
  • A test pins the failed finalize.

epic: #1437

Activity

  1. added a commit that references this issue on Nov 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:should-haveShould be done. Applied by the inbox-route classifier or a human.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0