feat: use mb-stack#116
Conversation
|
Warning Review limit reached
Next review available in: 53 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR updates the Pinocchio private-counter test to conditionally generate and fund an ephemeral keypair for local runs, tolerate missing TEE auth tokens, and refactors test-locally.sh to start and manage a single supervised mb-stack process instead of separate validator/service processes. ChangesPrivate-counter local test funding
Estimated code review effort: 3 (Moderate) | ~20 minutes mb-stack orchestration refactor
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@private-counter/pinocchio/tests/pinocchio-private-counter.test.ts`:
- Around line 55-62: The local keypair setup eagerly reads the fallback file
before the isLocal branch is applied, so local runs can still crash in the test
setup. Update the userKeypair initialization in
pinocchio-private-counter.test.ts so the fs.readFileSync call only happens in
the non-local path, and keep Keypair.generate() as the only path used when
isLocal is true; use the existing isLocal, KEYPAIR, and userKeypair symbols to
locate the fix.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 45eb6396-547e-4406-95db-43f358afa5d3
📒 Files selected for processing (2)
private-counter/pinocchio/tests/pinocchio-private-counter.test.tsscripts/test-locally.sh
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Summary by CodeRabbit
Bug Fixes
Chores