Opened from the recovery of issue 206 on 2026-10-03: the build seat's worker, re-made by hand and recreated by the controller with the default delivery policy on a stream that keeps history, replayed every build ask since 1 October; nine modules were re-registered from that commit and one machine got their old tools containers before the build machine was taken off. Two questions for HQ: whether a seat's work queue should keep acknowledged asks at all, and whether an outcome for a commit the catalogue has moved past should be recorded but never registered or rolled out. Checks pass.
Opened from the recovery of issue 206 on 2026-10-03: the build seat's worker, re-made by hand and recreated by the controller with the default delivery policy on a stream that keeps history, replayed every build ask since 1 October; nine modules were re-registered from that commit and one machine got their old tools containers before the build machine was taken off. Two questions for HQ: whether a seat's work queue should keep acknowledged asks at all, and whether an outcome for a commit the catalogue has moved past should be recorded but never registered or rolled out. Checks pass.
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.
Opened from the recovery of issue 206 on 2026-10-03: the build seat's worker, re-made by hand and recreated by the controller with the default delivery policy on a stream that keeps history, replayed every build ask since 1 October; nine modules were re-registered from that commit and one machine got their old tools containers before the build machine was taken off. Two questions for HQ: whether a seat's work queue should keep acknowledged asks at all, and whether an outcome for a commit the catalogue has moved past should be recorded but never registered or rolled out. Checks pass.