Skip to content

CI: fix a few issues and revert debug flag#51

Merged
tarekziade merged 3 commits into
mainfrom
remove-task-debug-cap
Jul 6, 2026
Merged

CI: fix a few issues and revert debug flag#51
tarekziade merged 3 commits into
mainfrom
remove-task-debug-cap

Conversation

@tarekziade

@tarekziade tarekziade commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Three related changes.

1. Drop the TASK_DEBUG_MAX_TASKS debug cap

Removes the temporary TASK_DEBUG_MAX_TASKS: "3" cap (and comment) from deploy/helm/env/prod.yaml. Added alongside runner crash self-reporting (#50) to keep manual triage retriggers short — its comment said "Remove once the runner-startup crash is diagnosed." Now the nightly triage runs the full batch again instead of only the first 3. The mechanism in reviewbot/webapp.py stays (unset = no cap) as a debug knob.

2. Fix ai-review.yml startup failure

trim() is not a valid GitHub Actions expression function, so its use in the job if: (added in #45) made the workflow fail to compile — a startup failure with zero jobs run, e.g. run 28783571654. Dropped it; startsWith(comment.body, '@askserge ') already enforces "@askserge as the first word", so #45's intent is preserved (only leading-whitespace tolerance is lost). Same fix applied to the workflow example in docs/github-action.md.

3. Lint workflows in CI so this can't recur

Adds an actionlint job to tests.yml that the test and helm jobs depend on (runs first, gates the rest). actionlint statically validates ${{ }} expressions — including that called functions exist — so an invalid function like trim() fails the PR check with a clear message instead of silently producing a zero-job startup failure. Pinned to actionlint v1.7.11.

🤖 Generated with Claude Code

tarekziade and others added 2 commits July 6, 2026 12:03
…atch

The debug cap (TASK_DEBUG_MAX_TASKS=3) was added alongside the runner
crash self-reporting (#50) to keep manual triage retriggers a short
crash-repro cycle. Now that the runner-startup crash is diagnosed and
self-reporting is in place, remove the temporary cap so serge executes
every /tasks request in a burst again.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
`trim()` is not a valid GitHub Actions expression function (the only
string helpers are contains/startsWith/endsWith/format/join). Using it
in the job `if:` made the workflow fail to compile — a startup failure
with zero jobs run (e.g. run 28783571654).

startsWith(comment.body, '@askserge ') already enforces "@askserge as
the first word" since it matches from the literal start of the body, so
dropping trim() keeps the #45 intent; we only lose tolerance for leading
whitespace before the mention, which is an acceptable edge case.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tarekziade tarekziade changed the title prod: drop TASK_DEBUG_MAX_TASKS debug cap prod: drop TASK_DEBUG_MAX_TASKS cap + fix ai-review workflow startup failure Jul 6, 2026
Add an `actionlint` job to tests.yml that the test/helm jobs depend on,
so workflow files are statically checked on every PR. actionlint
validates ${{ }} expressions (including that called functions exist),
which catches errors like the invalid trim() that broke ai-review.yml —
those otherwise surface only as a startup failure with zero jobs run.

Also fix the same invalid trim() in the docs/github-action.md workflow
example so users don't copy a workflow that fails to compile.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@tarekziade tarekziade changed the title prod: drop TASK_DEBUG_MAX_TASKS cap + fix ai-review workflow startup failure prod: drop debug task cap; fix + lint ai-review workflow Jul 6, 2026
@tarekziade tarekziade changed the title prod: drop debug task cap; fix + lint ai-review workflow CI: fix a few issues and revert debug flag Jul 6, 2026
@tarekziade tarekziade merged commit 31d88f6 into main Jul 6, 2026
3 checks passed
@tarekziade tarekziade deleted the remove-task-debug-cap branch July 6, 2026 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant