Found live at 00:34Z today, the first time a host carrying former targets (ADR 0163 rule 5, mesh-host 63) replaced itself (mesh-host 64): the new host's first apply asked to remove the previous version's directory as a former target of its own archive, an archive has no removal (issue 162), and the refusal ended every apply at its first step on all four machines.
Located in mesh-host's removeOrphan and Record. The fix is on mesh-host branch fix/a-former-target-without-a-removal-is-left-and-said: a former target of a kind the host cannot remove is left in place, said, and forgotten — never fatal; a dropped archive still refuses as 162 has it. The record also says what recovery takes, because the broken host cannot apply its own fix.
Issue number 194: main has up to 189, open PRs 271–273 hold 190–193.
Found live at 00:34Z today, the first time a host carrying former targets (ADR 0163 rule 5, mesh-host 63) replaced itself (mesh-host 64): the new host's first apply asked to remove the previous version's directory as a former target of its own archive, an archive has no removal (issue 162), and the refusal ended every apply at its first step on all four machines.
Located in mesh-host's `removeOrphan` and `Record`. The fix is on mesh-host branch `fix/a-former-target-without-a-removal-is-left-and-said`: a former target of a kind the host cannot remove is left in place, said, and forgotten — never fatal; a dropped archive still refuses as 162 has it. The record also says what recovery takes, because the broken host cannot apply its own fix.
Issue number 194: main has up to 189, open PRs 271–273 hold 190–193.
Rule 5 of ADR 0163 (a former target is removed) met issue 162 (an archive
has no removal) in the host's own archive, the first time a host carrying
former targets replaced itself; every machine applied nothing from then on.
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 live at 00:34Z today, the first time a host carrying former targets (ADR 0163 rule 5, mesh-host 63) replaced itself (mesh-host 64): the new host's first apply asked to remove the previous version's directory as a former target of its own archive, an archive has no removal (issue 162), and the refusal ended every apply at its first step on all four machines.
Located in mesh-host's
removeOrphanandRecord. The fix is on mesh-host branchfix/a-former-target-without-a-removal-is-left-and-said: a former target of a kind the host cannot remove is left in place, said, and forgotten — never fatal; a dropped archive still refuses as 162 has it. The record also says what recovery takes, because the broken host cannot apply its own fix.Issue number 194: main has up to 189, open PRs 271–273 hold 190–193.