Repository navigation
fix(mcp-status): read scoreboard from correct path - #166
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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.
Pull request overview
Fixes /nf:mcp-status incorrectly reporting an empty quorum scoreboard by updating the scoreboard file path to match the current .planning/ layout.
Changes:
- Update scoreboard lookup path from
.planning/quorum-scoreboard.jsonto.planning/quorum/scoreboard.json.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The skill looked for the scoreboard at `.planning/quorum-scoreboard.json` but it actually lives at `.planning/quorum/scoreboard.json` (note the directory separator vs hyphen). Every /nf:mcp-status run reported "Scoreboard: no data yet (run /nf:quorum first to populate)" even when quorum had run many times and the file existed with rounds populated. Live verification: before: file not found → reported 0 rounds after: found 10 rounds, captured_at 2026-05-13T07:06:43 Caught live today after running /nf:quorum which wrote 3 entries — the next /nf:mcp-status still said "no data yet" because of the stale path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6537edd to
4d338f6
Compare
Summary
/nf:mcp-statusalways reported "Scoreboard: no data yet (run /nf:quorum first to populate)" even when quorum had run successfully. It was looking for the scoreboard at.planning/quorum-scoreboard.jsonbut the file actually lives at.planning/quorum/scoreboard.json(note the directory separator vs hyphen).Caught live today: a fresh session ran
/nf:quorumwhich wrote 3 new entries to.planning/quorum/scoreboard.json, then/nf:mcp-statusstill said "no data yet" because of the stale path lookup.Live verification
Test plan
/nf:mcp-statusshows real scoreboard count + last update instead of "no data yet"🤖 Generated with Claude Code