mosaicstack/stack
25
0
Fork 1
Code Issues 340 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

fix(git-tools): ci-queue-wait — Gitea statuses:null no longer malformed; CI-less repos pushable again #1129

Merged
ops-02 merged 3 commits from fix/ci-queue-wait-no-status into next 2026-08-19 22:08:35 +00:00
Conversation 3 Commits 3 Files Changed 4
+213 -10
3 Commits
Author SHA1 Message Date
ops-02 c7965e787c fix(ci): satisfy sanitization + test-enumeration gates for #1129
ci/woodpecker/pr/ci Pipeline was successful
Details 
Two gates added to CI after this branch was written:

- verify-sanitized: the harness header named the operator repo the
  live payload was captured from. Genericized; the payload itself
  was already synthetic.
- check-test-enumeration (#1017): the new harness was not on any CI
  surface. Enumerated in test:framework-shell beside its three
  ci-queue-wait siblings.

All four ci-queue-wait suites green; both gates green locally.
 2026-08-19 16:36:28 -05:00
ops-02 96021e7795 Merge origin/next into fix/ci-queue-wait-no-status
ci/woodpecker/pr/ci Pipeline failed
Details 
Resolve against #1148's purpose-sensitive rewrite: keep next's
queue-clear message format and terminal-failure split, re-apply the
null-statuses tolerance and zero-contexts-first classification
(the half #1148 did not carry). All four ci-queue-wait suites green
on the merged tree.
 2026-08-19 16:30:05 -05:00
Jason WoltjeandClaude Fable 5 74b3b9e869 fix(git-tools): ci-queue-wait mishandles Gitea statuses:null — push guard hard-fails on any repo without CI
ci/woodpecker/pr/ci Pipeline failed
Details 
Gitea's combined-status endpoint returns statuses:null (not []) plus a
synthetic aggregate state of "pending" for a commit with zero status
contexts (captured live 2026-08-09). The bash parser called that payload
malformed -> ASSERTED_NOT_READY exit 3, blocking every push to a CI-less
repo; hit twice by velma on two independent clones (shared checkout +
fresh sparse clone), proving it environment-independent.

- treat statuses:null as empty (both .sh and .ps1)
- classify zero contexts as no-status BEFORE consulting the synthetic
  aggregate state (both twins; honoring it would poll to timeout)
- no-status on --purpose push without --require-status is now queue-clear
  exit 0 (a repo with no CI has no queue), mirroring record_cannot_assert
  dispositions (push=degraded-pass, merge=hold); merge + --require-status
  stay fail-closed at exit 3
- red-first regression harness test-ci-queue-wait-no-status.sh (5 cases,
  incl. the verbatim live Gitea payload and a genuine-pending guard);
  branch-absent harness still green

Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_013SAYFkRhQfhguY7AHfiUC8
 2026-08-09 03:02:25 -05:00