(MOT-4299) fix(ci): coerce the deployed E2E dispatch runs input to a number - #703
Conversation
…number 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.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
skill-check — worker0 verified, 54 skipped (no docs/).
Four for four. Nicely done. |
|
Warning Review limit reached
Next review available in: 4 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 |
1 participant
Second startup killer in
harness-e2e-deployed.ymldispatch, surfaced immediately after #702 cleared the input-count cap (30966815754, zero jobs, same opaque banner, head_sha already on fixed main).workflow_dispatch delivers
type: numberinputs as strings in theinputscontext; forwardinginputs.runsinto_harness-e2e.yml'sruns(type: number) fails the callee's startup type check. Push-triggered callers pass literals, so only manual dispatch dies — and this wrapper had never been dispatched before tonight. actionlint cannot catch this one (runtime evaluation, not schema).Fix:
runs: ${{ fromJSON(format('{0}', inputs.runs || 1)) }}— coerces both the explicit-string and untouched-default shapes.