Found on the first adopted node, when the first web module could not be assigned: nothing provides route.
Every module reachable by name requires a route. The mesh has one provider, its own proxy, which binds the two public ports on the machine's own network and cannot be moved by a node's port setting. The predecessor's proxy holds those ports. So a web module cannot be taken until the mesh's proxy runs, the mesh's proxy cannot run until the predecessor's stops, and when it stops every name it serves goes dark — because the successor serves only what mesh modules contributed.
Adoption covers a file kept as it was and a container kept as it was. It has nothing for a service whose successor is different software: nothing shares a name to hold, so there is only replacement, of every name at once.
The proxy is the first case, not the only one: any provision with a single provider owning a scarce machine-wide port has this shape.
Found on the first adopted node, when the first web module could not be assigned: nothing provides `route`.
Every module reachable by name requires a route. The mesh has one provider, its own proxy, which binds the two public ports on the machine's own network and cannot be moved by a node's port setting. The predecessor's proxy holds those ports. So a web module cannot be taken until the mesh's proxy runs, the mesh's proxy cannot run until the predecessor's stops, and when it stops every name it serves goes dark — because the successor serves only what mesh modules contributed.
Adoption covers a file kept as it was and a container kept as it was. It has nothing for a service whose successor is different software: nothing shares a name to hold, so there is only replacement, of every name at once.
The proxy is the first case, not the only one: any provision with a single provider owning a scarce machine-wide port has this shape.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found on the first adopted node, when the first web module could not be assigned: nothing provides
route.Every module reachable by name requires a route. The mesh has one provider, its own proxy, which binds the two public ports on the machine's own network and cannot be moved by a node's port setting. The predecessor's proxy holds those ports. So a web module cannot be taken until the mesh's proxy runs, the mesh's proxy cannot run until the predecessor's stops, and when it stops every name it serves goes dark — because the successor serves only what mesh modules contributed.
Adoption covers a file kept as it was and a container kept as it was. It has nothing for a service whose successor is different software: nothing shares a name to hold, so there is only replacement, of every name at once.
The proxy is the first case, not the only one: any provision with a single provider owning a scarce machine-wide port has this shape.