Fix eval: set up in current directory, not subdirectory#24
Conversation
Root cause of 0/28 failure: init-project.js --name=myapp creates a myapp/ subdirectory, but the grader checks the temp dir root. Prompts now explicitly say "IN THE CURRENT DIRECTORY — do not create a subdirectory" for all three fixtures. Added gotcha to CLAUDE.md. https://claude.ai/code/session_01Hbxy31TkbujzukGFSxLcPw
|
Warning Rate limit exceeded
⌛ 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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ 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 |
Summary
Root cause of 0/28 setup eval failure:
init-project.js --name=myappcreates amyapp/subdirectory inside the temp dir, but the grader checks the temp dir root. All files existed but in the wrong place.Test plan
npx jest --config '{}' tests/scripts/— 112 tests passbash tests/evals/run-evals.sh --config setup-eval-config.json --dry-run— prompts show directory guidancehttps://claude.ai/code/session_01Hbxy31TkbujzukGFSxLcPw