Conversation
Install the sha256-pinned npm tarball instead of resolving name@version at build time. The tarball ships npm-shrinkwrap.json, which locks the transitive dependency tree; two --no-cache builds produce identical content-addressed output. Addresses PR review.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 8 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Comment |
…aming The previous commit said tamarin "builds on arm64 and fails on amd64", and treated it as the onboarding's amd64-unverified flag finally coming due. That was wrong, and wrong in a way that would mislead the next reader. pkgs#607 and #608 built the SAME tamarin source on the SAME amd64 builder and passed — merged 20:28 and 20:30 on 2026-08-14, hours after #606 failed at 12:33. So amd64 works most of the time. It is not a miscompile, not a missing dependency, and not something #606 introduced: it is a race, and #606 drew the short straw. This strengthens the fix rather than weakening it — removing cabal's own store-provisioned alex removes the racy step — but the diagnosis in the comment should say what is actually true. Worth recording why a flake is the worse shape here: the natural response is to re-run it, which usually works, which is exactly how one survives for weeks without anyone fixing it. If this change does NOT settle it, the next suspect is `--jobs=$(nproc)` itself rather than alex specifically, since the same race can bite any build tool. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add a package for maki 0.4.7, a Rust TUI AI coding agent (github.com/tontinton/maki).
Changes
packages/maki/build.nclmaki --versiontestpackages/maki/build.shcargo build --release --locked --bin makiwith Rust and C determinism flags (path remaps, prefix map)Notes:
makeandperlare required because isahc builds vendored OpenSSL from source (static-ssl).toolchainships neither.include_dir!, so the package ships only the binary.needs = { dns, internet }for cargo fetches;Cargo.lockis committed, so the build uses--locked.Verification
mip check --packages maki: all 15 checks pass, includingmissing runtime_depsand the standalone testmip package buildandmip package build --rebuild) produce byte-identical output (same content-addressed hash;diff -rclean)maki --versionprintsmaki 0.4.7