fix(runner): keep harbor waiting truth ahead of stale jobs
Some checks failed
CD Pipeline / workflow-shape (push) Successful in 0s
CD Pipeline / cancel-stale-cd (push) Has been skipped
CD Pipeline / tests (push) Successful in 35s
CD Pipeline / build-and-deploy (push) Failing after 2m37s
CD Pipeline / post-deploy-checks (push) Has been skipped

This commit is contained in:
Your Name
2026-07-01 09:25:13 +08:00
parent 83b7aa491e
commit 7bd1b1b2a4
3 changed files with 27 additions and 10 deletions

View File

@@ -1,3 +1,17 @@
## 2026-07-01 — 09:24 Harbor repair waiting truth / public route blocker
**照主線修正的問題**
- 188 runner re-enable 後live queue 已從 `awoooi-non110-*` no-matching 進展到 Harbor repair waiting但 Gitea unauthenticated jobs API 仍回 `ai-code-review` 或 CD workflow jobs造成 reader 將 visible waiting 誤升級為 `harbor_110_repair_jobs_stale_or_mismatched`
- `ops/runner/read-public-gitea-actions-queue.py` 調整 status 優先序:當 visible Harbor repair run 為 waiting 且 no-matching 為空時,主狀態維持 `harbor_110_repair_waiting_for_runner_or_queue` / `blocked_harbor_110_repair_workflow_waiting`stale / cross-workflow jobs payload 仍保留在 readback / rollups 作為 evidence不再覆蓋 visible queue truth。
- 後續 live queue 已前進到 CD `#4211 Failure`classifier=`harbor_registry_public_route_unavailable`、status code `502`Harbor repair `#4212 Failure`、no-matching 空public registry `/v2/``502`。目前主線 blocker 已不是 runner label而是 110 Harbor public route / repair failure。
**驗證**
- `python3.11 -m pytest ops/runner/test_read_public_gitea_actions_queue.py -q` 通過30 passed
- `DATABASE_URL='postgresql+asyncpg://awoooi:awoooi_test_2026@127.0.0.1:5432/awoooi_test' python3.11 -m pytest apps/api/tests/test_harbor_registry_controlled_recovery_receipt.py ops/runner/test_verify_awoooi_non110_cd_closure.py -q` 通過26 passed
- `python3.11 -m py_compile ops/runner/read-public-gitea-actions-queue.py``git diff --check` 通過。
**邊界**:只改 public Gitea queue readback parser / tests / LOGBOOK未讀 token / secret / `.env` / raw sessions / SQLite / auth未使用 GitHub / `gh` / GitHub API未 workflow_dispatch未新增 host write、未重啟主機、未 restart Docker / Nginx / K3s / DB / firewall。
## 2026-07-01 — 09:18 non-110 runner runtime re-enable / queue no-matching cleared
**照主線修正的問題**