Measured while planning the control-node's migration: 14 of 46 modules with containers fix the machine side of a published port in the definition, 32 leave it to the node.
Two kinds are defensible — the foundation's own ports, which are rewritten at genesis and are now per-node settings, and ports a protocol fixes by number. The rest are a predecessor's host ports copied in during conversion: facts about one machine written into a definition meant for any machine.
Not fatal, since a node's ports setting overrides the mapping's machine side, and for this migration the copied numbers happen to be the right ones. But the default is in the wrong place and nothing says so when a module is written. The conversion backlog is where this gets decided for the modules still to be written, which is why it is worth answering now.
Measured while planning the control-node's migration: 14 of 46 modules with containers fix the machine side of a published port in the definition, 32 leave it to the node.
Two kinds are defensible — the foundation's own ports, which are rewritten at genesis and are now per-node settings, and ports a protocol fixes by number. The rest are a predecessor's host ports copied in during conversion: facts about one machine written into a definition meant for any machine.
Not fatal, since a node's `ports` setting overrides the mapping's machine side, and for this migration the copied numbers happen to be the right ones. But the default is in the wrong place and nothing says so when a module is written. The conversion backlog is where this gets decided for the modules still to be written, which is why it is worth answering now.
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.
Measured while planning the control-node's migration: 14 of 46 modules with containers fix the machine side of a published port in the definition, 32 leave it to the node.
Two kinds are defensible — the foundation's own ports, which are rewritten at genesis and are now per-node settings, and ports a protocol fixes by number. The rest are a predecessor's host ports copied in during conversion: facts about one machine written into a definition meant for any machine.
Not fatal, since a node's
portssetting overrides the mapping's machine side, and for this migration the copied numbers happen to be the right ones. But the default is in the wrong place and nothing says so when a module is written. The conversion backlog is where this gets decided for the modules still to be written, which is why it is worth answering now.