|
All checks were successful
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 19s
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 15s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 18s
CI / Detect changes (pull_request) Successful in 55s
sop-tier-check / tier-check (pull_request) Successful in 20s
E2E API Smoke Test / detect-changes (pull_request) Successful in 55s
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 59s
Handlers Postgres Integration / detect-changes (pull_request) Successful in 1m3s
Runtime PR-Built Compatibility / detect-changes (pull_request) Successful in 54s
CI / Platform (Go) (pull_request) Successful in 14s
CI / Canvas (Next.js) (pull_request) Successful in 10s
CI / Shellcheck (E2E scripts) (pull_request) Successful in 12s
CI / Python Lint & Test (pull_request) Successful in 14s
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 14s
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 10s
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 13s
Runtime PR-Built Compatibility / PR-built wheel + import smoke (pull_request) Successful in 9s
audit-force-merge / audit (pull_request) Successful in 24s
CI / Canvas Deploy Reminder (pull_request) Has been skipped
GitHub releases are unreachable from Gitea Actions runners on 5.78.80.188 — curl to github.com times out after ~3s instead of waiting for the 60s timeout. The previous GitHub-first / apt-get-fallback approach always hit the timeout and never reached apt-get. Changes: - `.gitea/workflows/sop-tier-check.yml`: Install jq step now tries apt-get first, then GitHub binary as secondary fallback. Extended timeout to 120s for the GitHub download in case it is reachable on some runner networks. - `.gitea/scripts/sop-tier-check.sh`: script-level fallback also uses apt-get first, then GitHub, then respects SOP_FAIL_OPEN=1 (set in workflow step) to exit 0 so CI never blocks. Combined with continue-on-error: true at step level and SOP_FAIL_OPEN=1, this makes sop-tier-check CI resilient to any jq installation failure. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| tests | ||
| audit-force-merge.sh | ||
| ci-required-drift.py | ||
| main-red-watchdog.py | ||
| sop-tier-check.sh | ||