Repository navigation
v0.13.48
Patch Changes
-
b785ff8:
fleet:deployregisters thea11ysrvtask before it restarts it, reads the registered action back and refuses a box whose task does not start the published launcher (A11-204). The deploy used to restart a task it never registered, so a box whose task still started the laidpackages\nvda-worker\src\run-server.cmd(an orphan since a11ign/a11ign#5546, v0.9.0 on a11y-worker-11) kept serving that tree through the restart and through the rebootverify-code.ymlescalates to: the logon trigger starts the registered action, not the code the deploy laid. The two registration steps move unchanged fromroles/worker/tasks/tasks.ymlintoroles/worker/tasks/worker-task.yml, which the role imports anddeploy.ymlruns, so the registration is defined once.fleet:statusreads each box's worker code (/health.code) as a fourth field of the build split: a code split, or a reachable box that reports no code, printsfleet BUILD SPLIT — Worker code: <hash> on <boxes>; …and exits 3, and an agreeing fleet names its one code in thefleet builds AGREEline. The oldfleet SPLIT — N different code hashesline, which named no box, said "Nothing is broken" and exited 0, is gone;codesstays in--json.