Repository navigation
Retry bun install in CI - #91
Conversation
bun sometimes fails to extract a large tarball on runners ("Fail
extracting tarball for next"), which failed Lint twice on main and on a
PR. Every install now goes through .github/scripts/bun-install.sh, which
retries twice with a short backoff; the lockfile is frozen, so a retry can
only produce the same install. The app workflow now installs with
--frozen-lockfile like the others.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (11)
Limit details: You’ve used all 2 included reviews currently available. Your 73 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. 📜 Recent review details⏰ Context from checks skipped due to timeout. (9)
🧰 Additional context used🪛 zizmor (1.30.1).github/workflows/infra-ci.yaml[warning] 3-17: insufficient job-level concurrency limits (concurrency-limits): workflow is missing concurrency setting (concurrency-limits) .github/workflows/cli.yaml[warning] 3-21: insufficient job-level concurrency limits (concurrency-limits): workflow is missing concurrency setting (concurrency-limits) 🔇 Additional comments (11)
📝 WalkthroughWalkthroughA shared Bash script retries frozen-lockfile Bun installs up to three times. GitHub Actions workflows use the script for dependency installation, and several workflows trigger when the script changes. ChangesBun dependency installation
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Sequence Diagram(s)sequenceDiagram
participant Workflow as GitHub Actions job
participant Script as bun-install.sh
participant Bun as bun install
Workflow->>Script: Run shared install script
loop Up to three attempts
Script->>Bun: Run frozen-lockfile install
Bun-->>Script: Return install status
end
Script-->>Workflow: Exit with success or failure status
Merge Risk: ⚪ Minimal · up to The shared installer is wired into the reviewed CI workflows, including their subdirectory install steps. No actionable merge-blocking regression is evident. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
✨ Simplify code
Usage-based review receipt
Note This review was completed with usage-based billing: files reviewed beyond your plan's included limits are billed at $0.25/file. View usage-based billing. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This branch was successfully deployed
1 participant
Preview · Change Stack · Checks · Files: +48 −20 in 11 files
bun sometimes fails to extract a large package tarball on GitHub's runners (
error: Fail extracting tarball for "next"). That failed the Lint job twice today, once on main after #83 and once on #72, and both times a rerun passed.bun installstep now runs.github/scripts/bun-install.sh, which retries twice with a short backoff and emits a warning annotation on each retry, so a flaky run stays visible. The lockfile is frozen, so a retry can only produce the same install.--frozen-lockfile; it now uses it like every other workflow.