jschoubben
668ce3ad62
Issue 094 resolved: a given port names either end and is answered once
...
The first pass answered under both ends, which review showed is the same fault seen
from the other side where two mappings share a number. Verified on the machine: the
forge is back on the port its own configuration has always advertised.
2026-09-23 02:37:07 +02:00
jschoubben
0c8615aa8f
Issue 098: taking a module replaces a configuration nobody compared
...
Found reading the second module's cutover rather than running it: the catalogue's
config drops a rule the machine's has, and no step puts the two side by side.
2026-09-23 02:23:58 +02:00
jschoubben
235b9ea0e5
Issues 096 and 097, and 094 diagnosed: a setting stored where it cannot work, and a resource that changed target
...
094's cause is one blind spot read from two ends, written up in its diagnosis; the fix
answers the first open question and not the other two, which become 096. 097 was found
looking at what the forge's cutover left running.
2026-09-23 02:20:48 +02:00
jschoubben
1b8e5043ee
Merge pull request 'Issues 094 and 095, both found in the first module's cutover' ( #83 ) from issues/094-095-from-the-first-cutover into main
2026-09-22 23:57:48 +00:00
jschoubben
515cb8adc1
Issues 094 and 095, both found in the first module's cutover
2026-09-23 01:57:10 +02:00
jschoubben
0d8b683ad7
Merge pull request 'Research 013: the forge and the registries — a seat answers the wrong question' ( #82 ) from research/013-the-forge-and-the-registries into main
2026-09-23 01:03:10 +02:00
jschoubben
43b55d6664
Research 013: the forge and the registries — a seat answers the wrong question; issues 090 and 085 corrected from the code
2026-09-23 00:38:34 +02:00
jschoubben
6c81ea2204
Merge pull request 'ADR 0104: a provision may be answered by an adapter to the predecessor' ( #81 ) from decide/0104-route-adapter into main
2026-09-22 23:57:54 +02:00
jschoubben
a23ede495e
ADR 0104: a provision may be answered by an adapter to the predecessor; issue 093 located; connectivity says how the proxy hands over
2026-09-22 23:57:38 +02:00
jschoubben
a2323ade2e
Merge pull request 'Issue 093: the successor proxy cannot serve what the predecessor still serves' ( #80 ) from issue/093-proxy-handover into main
2026-09-22 23:57:04 +02:00
jschoubben
d697c6f776
Issue 093: the successor proxy cannot serve what the predecessor still serves, so no web module can migrate one at a time
2026-09-22 23:45:49 +02:00
jschoubben
a7b3f7823b
Issue 092: it happened twice more — the registry's mesh name, and the mesh's own trust naming the default port
2026-09-22 23:37:05 +02:00
jschoubben
cc3af29084
Issue 092: genesis publishes to a registry the container runtime does not yet trust
2026-09-22 22:43:17 +02:00
jschoubben
fb9d3035d4
Issue 091: a module definition carries a machine port, measured across the catalogue
2026-09-22 22:26:14 +02:00
jschoubben
dd81523eab
Merge pull request 'Issue 085 resolved' ( #77 ) from fix/085-resolved into main
2026-09-22 22:00:49 +02:00
jschoubben
5c5821b210
Issue 085 resolved: the packages port is a node setting; two of its open questions stay open
2026-09-22 22:00:38 +02:00
jschoubben
c46c508c03
Merge pull request 'Issues 088, 089 and 090, found fixing 085' ( #76 ) from fix/issue-085-followups into main
2026-09-22 22:00:02 +02:00
jschoubben
1728765fe3
Issues 089 and 090: a contributed route does not follow a moved port; the forge module cannot take over the forge genesis raised
2026-09-22 21:54:35 +02:00
jschoubben
e609ccdbfb
Issue 088: the forge's own address names a port it may not have
2026-09-22 21:41:58 +02:00
jschoubben
60eae92fb1
Merge pull request 'Adoption mode as built: ADRs 0101–0103, issues 084–086' ( #75 ) from feat/adoption-mode into main
2026-09-22 21:02:00 +02:00
jschoubben
7bbbfb158a
ADR 0103: a unit is found when an administrator installed it or the machine uses it
2026-09-22 20:02:18 +02:00
jschoubben
87ae893407
Issue 087: the controller cannot tell that a node's host is too old for what it sends
2026-09-22 19:43:01 +02:00
jschoubben
c74ea2a4a8
Records say what the build does: 0101 names only measured daemons; 0102 adds to lists and keeps what it writes over; 0103 names every held kind, the found-service rule, conflicting found rules, guards, and what of 0100 it replaces; designs 05, 09 and 17 in step; issue 084's diagnosis in its own file
2026-09-22 19:38:16 +02:00
jschoubben
ca1f648973
Issue 086: taking a module narrows a port the predecessor served, without saying so
2026-09-22 19:00:59 +02:00
jschoubben
019184ec0f
Issue 085: the packages port given at genesis is not a setting, and a later module can undo it
2026-09-22 18:17:21 +02:00
jschoubben
213ab898d6
ADR 0103: what an adopted node holds and what its guard refuses; the node host and connectivity designs name 0102 and 0103
2026-09-22 17:52:58 +02:00
jschoubben
84761f0600
ADR 0102: the mesh writes into a shared file, never over it; issue 084 located
2026-09-22 17:46:06 +02:00
jschoubben
1901a90d68
ADR 0101 accepted; raising a mesh names it
2026-09-22 17:43:13 +02:00
jschoubben
347bbce633
ADR 0101 proposed: a machine's own resolver does not make it in use, as measured on a fresh machine
2026-09-22 17:38:44 +02:00
jschoubben
6165a7ae02
Issue 084: taking networking on an adopted node restarts every container, and the held runtime file blocks pulling
2026-09-22 17:09:21 +02:00
jschoubben
dfadfd23c0
Merge pull request 'ADR 0100 (proposed): a node in use is adopted before it is converged' ( #74 ) from feat/adoption-mode into main
2026-09-22 16:35:32 +02:00
jschoubben
3d4ab23830
ADR 0100: the machine's own traffic is known by its interface, not its source address
2026-09-22 16:35:25 +02:00
jschoubben
37252f9c3e
ADR 0100: the guard lets the machine itself through; in use is a non-loopback listener; openings say from where; 09 in step with the flip
2026-09-22 16:34:53 +02:00
jschoubben
f3152d827f
ADR 0100 after re-review: the bus and registry stay reachable for enrolment; the mesh guards the store in a table that only refuses; a machine in use defined; the flip refuses while a found container is held; held containers and returning to adopted spelled out
2026-09-22 16:32:37 +02:00
jschoubben
02c40bcab4
ADR 0100 after review: found means unrecorded; assigning prepares, taking cuts over; openings through the found firewall on both paths; the mesh guards its own ports; ports kept as node settings; a converged genesis refuses a machine in use; designs 05, 07, 08, 09 and 17 in step
2026-09-22 16:28:31 +02:00
jschoubben
111456abb5
ADR 0100 accepted; the node host, connectivity, the node lifecycle and raising a mesh amended for a node adopted before it is converged
2026-09-22 16:20:27 +02:00
jschoubben
5fc3cbde4c
Research 012: migrating a node that is in use, measured on the control-node; ADR 0100 proposed — a node in use is adopted before it is converged
2026-09-22 16:16:28 +02:00
jschoubben
21baf397a8
Merge pull request 'Issue 083 resolved: nothing the control queue carries is lost while the store restarts' ( #73 ) from multiple-fixes into main
2026-09-22 14:43:00 +02:00
jschoubben
4de74880cb
Issue 083: the proof, the replay caveat, and what is not closed, as three reviews found them
2026-09-22 14:39:29 +02:00
jschoubben
266ee34b5c
Issue 083: the diagnosis describes held messages, the enrolment's order, and what is not closed
2026-09-22 14:24:31 +02:00
jschoubben
2d45aa5f42
Issue 083 resolved: nothing the control queue carries is lost while the store restarts; an enrolment claims its token and spends it last
2026-09-22 14:11:44 +02:00
jschoubben
4e74cf29e4
Merge pull request 'Issues 081 and 082 resolved; 083 opened' ( #72 ) from multiple-fixes into main
2026-09-22 13:53:16 +02:00
jschoubben
0d40918e92
Issue 081: proven by the two-node bed, and what it found about baserow's data directory
2026-09-22 13:53:00 +02:00
jschoubben
f6ded3102d
Issue 083 opened (other control messages lost while the store restarts); 082's diagnosis carries its review
2026-09-22 13:34:05 +02:00
jschoubben
9a75f2b6a9
Issue 082: a report that arrives while the store restarts was lost; 081's diagnosis corrected on review
2026-09-22 13:25:33 +02:00
jschoubben
5d1a0372cb
Issue 081 resolved: neither cache consumer can keep its keys under its login, so neither takes the shared cache
2026-09-22 12:27:12 +02:00
jschoubben
f1e3925009
Merge pull request 'Issues 079 and 080, found by running the large mesh bed; 074's addendum' ( #71 ) from multiple-fixes into main
2026-09-22 02:19:17 +02:00
jschoubben
35e44c3e5e
Issue 081 opened (a cache consumer does not use its login); 079 and 080 diagnoses carry the review's consequences
2026-09-22 02:04:29 +02:00
jschoubben
f760bf632c
Issue 080: a cache grant let the consumer flush the server; 079: the names follow the resolver's rule for the private network
2026-09-22 01:39:29 +02:00
jschoubben
e31e077fc8
Issue 079: the suffix is handed down, not written twice
2026-09-22 01:27:53 +02:00
jschoubben