novox/hq
3
0
Fork 0
Code Issues 4 Pull Requests Releases Wiki Activity

Two records were numbered 127; the second becomes 149, and is resolved

Browse Source 
A number identifies a record, and two were given 127 on 2026-09-27. The one
three documents and three source files cite by number keeps it; the other
becomes 149, says so in its own heading, and its two inbound references are
repointed.

It is also resolved: an empty declaration is sent carrying owns_nothing rather
than skipped, and the host refuses an empty body that does not carry it, so
emptiness cannot be read as a truncated declaration.
This commit is contained in:
jschoubben
2026-09-29 22:33:40 +02:00
parent 4eb16f1028
commit 96bdffa9bc
3 changed files with 24 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
04-ISSUES/130-undeclaring-a-service-stops-it/00-report.md
+1 -1
View File
@@ -16,7 +16,7 @@ found that the host's `remove` path stops every `service` resource that is no lo
delete". `store.Orphans` matches by id alone. So any of these stops the unit:
- the module is unassigned — by mistake, or to switch it for another;
- the node is sent a deliberately-empty declaration ([issue 127](../127-a-declaration-that-shrinks-to-empty-is-skipped-not-sent/00-report.md));
- the node is sent a deliberately-empty declaration ([issue 149](../149-a-declaration-that-shrinks-to-empty-is-skipped-not-sent/00-report.md));
- a later catalogue version renames the resource's `id`.
That is right for a service the mesh brought into being. It is wrong for a unit the mesh