(MOT-4299) fix(ci): fit harness-e2e-deployed dispatch inputs under GitHub's cap - #702
Conversation
…tHub's cap workflow_dispatch allows at most 10 inputs; the deployed wrapper declared 11, so every manual dispatch died at startup with the opaque 'workflow file issue' banner and zero jobs — push-triggered callers never hit the limit, which is why the release path masked it. Drop the judge_model/judge_provider overrides: both already resolve from repo vars, which remain the operator control surface. Caught by actionlint.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 18 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
…number (#703) workflow_dispatch delivers number-typed inputs as strings in the inputs context, so forwarding inputs.runs into _harness-e2e.yml's 'runs' (type: number) fails the callee's type check at startup — the run dies with the bare 'workflow file issue' banner and zero jobs, after #702 already cleared the input-count cap. Push-triggered callers pass literals and never hit it. fromJSON(format(...)) coerces both the string and the untouched-default shape.
1 participant
Every manual dispatch of
harness-e2e-deployed.ymlfailed at startup with the opaque "This run likely failed because of a workflow file issue" and zero jobs (30965720679, 30966132857). GitHub's API exposes no error detail; actionlint pinpointed it instantly:Push-triggered reusable-workflow callers don't traverse this validation, so the release pipeline path never surfaced it — the wrapper (new in #692/#694) had simply never been dispatched.
Fix: drop the
judge_model/judge_providerdispatch overrides (10→9 inputs would be 11→9). Both already fall back toHARNESS_E2E_JUDGE_MODEL/HARNESS_E2E_JUDGE_PROVIDERrepo vars, which remain the operator control surface;subjectsstays for one-off model tests.Worth considering as follow-up: an actionlint job in CI — it also validates reusable-workflow contracts that GitHub only checks at dispatch time.