A dead tracker is not the machine's failure (hq ADR 0187) #12

2026-10-02T18:41:48Z

mesh-admin commented

2026-10-02 18:41:48 +00:00

The home server has not applied cleanly since midday: the downloads step exited non-zero forty-nine times over six hours for one public tracker that stopped answering. A clean apply gates the found firewall's retirement, so a dead tracker was holding a firewall record hostage.

The step already had the rule — an entry the mesh only found and re-pointed is said and left as found — but it matched one shape only. An app can refuse to save such an entry, and it can save it and then fail its own test, because saving validates settings while the test runs a live search. The second shape failed the whole apply. What decides is now whose entry it is: one the mesh found is a notice, one the operator listed in the step's settings is still a failure.

Lands in all four Servarr modules, which carry byte-identical copies. The test uses the home server's own error message and models the app's two validations apart; it fails against the previous condition. Fifteen tests pass in each module.

The home server has not applied cleanly since midday: the downloads step exited non-zero forty-nine times over six hours for one public tracker that stopped answering. A clean apply gates the found firewall's retirement, so a dead tracker was holding a firewall record hostage. The step already had the rule — an entry the mesh only found and re-pointed is said and left as found — but it matched one shape only. An app can refuse to save such an entry, and it can save it and then fail its own test, because saving validates settings while the test runs a live search. The second shape failed the whole apply. What decides is now whose entry it is: one the mesh found is a notice, one the operator listed in the step's settings is still a failure. Lands in all four Servarr modules, which carry byte-identical copies. The test uses the home server's own error message and models the app's two validations apart; it fails against the previous condition. Fifteen tests pass in each module.

mesh-admin added 1 commit 2026-10-02 18:41:48 +00:00

A dead tracker is not the machine's failure (hq ADR 0187) 1a2f48492d

The step already left a found feed as found when the app refused to save it. An app can also save
it and then fail its own test — saving validates settings, the test runs a live search — and that
shape failed the whole apply. One dead public tracker stopped the home server converging for six
hours, and a clean apply gates the found firewall's retirement, so a tracker was holding a firewall
record hostage. What decides is whose entry it is: one the mesh only found is a notice, one the
operator listed is still a failure. All four copies of the step, and a test with the machine's own
message that models the app's two validations apart.

mesh-admin merged commit 5eee14ee0a into main

2026-10-02 18:41:55 +00:00

mesh-admin deleted branch fix/a-dead-tracker-is-not-the-meshs-failure

2026-10-02 18:41:55 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-media-catalog#12