The assigner never keeps a want back because a provider is unhealthy, and the canary gates only modules that run (issue 1960)

Conversation 2 Commits 1 Files Changed 3

+151 -53

1 Commits

Author	SHA1	Message	Date
jschoubben	d54eab4052	Never keep a want back for an unhealthy provider, nor a first want for the canary where nothing runs: the module is wanted and its provider down is said (issue 1960) mesh/delivery merged: source.main moved to novox/mesh-delivery@5e931eac191a Details mesh/delivery-group group fix/1960-no-hold-spread merged: every member is merged Details mesh/check pass d54eab4052d1 on c1b4533201c8 \| unit 3318 run, 1951 kept, 38 skipped \| integration 3994 run, 2125 kept, 38 skipped \| over bound: unit, … On novox on 2026-10-29 the assigner wrote no want for de-spiegel and link2pay (rule 5: no provider of route runs healthy) nor photos (rule 5: no provider of s3-bucket), and none where no node of a module was online (rule 3). A module with no want is on no list and nothing applies it; a site runs while the proxy in front of it is down. - Quick fix: skip rules 3 and 5 for the three modules' first wants. Leaves rule 5 holding every move and the canary holding new assignments. - Thorough fix, chosen: rule 5 holds no want; it is said per node (Outcome.Unreached, journaled once per words by the pass). The canary (rule 3) no longer holds the first want of a node that does not run the module. A node that runs it keeps the canary order: at an older composed and granted fingerprint of the new form its first want stays at what it runs; at an old-form build it waits for the canary as before (issue 1945); at an older fingerprint with no composition or grant it gets F. This departs from ADR 0429 §6, which makes every provider healthy a rule of every want. Tests: rows changed in the existing rule tests, and rows for today's modules (route-proxy down: de-spiegel and link2pay wanted; minio not healthy: photos moves; novox offline: a first want written, a move kept back).	2026-10-29 16:04:39 +01:00

Author

SHA1

Message

Date

jschoubben

d54eab4052

Never keep a want back for an unhealthy provider, nor a first want for the canary where nothing runs: the module is wanted and its provider down is said (issue 1960)

mesh/delivery merged: source.main moved to novox/mesh-delivery@5e931eac191a

Details

mesh/delivery-group group fix/1960-no-hold-spread merged: every member is merged

Details

mesh/check pass d54eab4052d1 on c1b4533201c8 | unit 3318 run, 1951 kept, 38 skipped | integration 3994 run, 2125 kept, 38 skipped | over bound: unit, …

On novox on 2026-10-29 the assigner wrote no want for de-spiegel and link2pay (rule 5: no provider of route runs
healthy) nor photos (rule 5: no provider of s3-bucket), and none where no node of a module was online (rule 3). A
module with no want is on no list and nothing applies it; a site runs while the proxy in front of it is down.

- Quick fix: skip rules 3 and 5 for the three modules' first wants. Leaves rule 5 holding every move and the
  canary holding new assignments.
- Thorough fix, chosen: rule 5 holds no want; it is said per node (Outcome.Unreached, journaled once per words by the
  pass). The canary (rule 3) no longer holds the first want of a node that does not run the module. A node that runs
  it keeps the canary order: at an older composed and granted fingerprint of the new form its first want stays at what
  it runs; at an old-form build it waits for the canary as before (issue 1945); at an older fingerprint with no
  composition or grant it gets F. This departs from ADR 0429 §6, which makes every provider healthy a rule of every want.

Tests: rows changed in the existing rule tests, and rows for today's modules (route-proxy down: de-spiegel and
link2pay wanted; minio not healthy: photos moves; novox offline: a first want written, a move kept back).

2026-10-29 16:04:39 +01:00

The assigner never keeps a want back because a provider is unhealthy, and the canary gates only modules that run (issue 1960) #110