-
Notifications
You must be signed in to change notification settings - Fork 8
feat: add GitHub API rate limit logging to solve command #1011
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Adding CLAUDE.md with task information for AI processing. This file will be removed when the task is complete. Issue: #1002
Add logging of GitHub API rate limit usage at key points during solve command execution to help identify expensive operations. - Add github-rate-limit-logger.lib.mjs module for rate limit tracking - Log rate limits at session start, after repo setup, after PR setup, after AI tool execution, and session summary - Add --github-rate-limits-logging flag (enabled by default) - Add delta tracking to identify API calls per operation - Add test experiment script Fixes #1002 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This reverts commit e23e2d6.
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
|
Resolve conflicts. The core issue was that we have some command, that stuck and was spending lots of GitHub API limits, so instead of |
|
🤖 AI Work Session Started Starting automated work session at 2026-01-11T01:51:08.374Z The PR has been converted to draft mode while work is in progress. This comment marks the beginning of an AI work session. Please wait working session to finish, and provide your feedback. |
…ault - Resolve merge conflict in src/solve.config.lib.mjs - Change --github-rate-limits-logging to be disabled by default - Update logging logic to check for `=== true` instead of `!== false` - Update changeset and test files to reflect new behavior Per feedback: logging can be enabled with --github-rate-limits-logging when debugging API usage issues. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
🤖 Changes AppliedBased on your feedback, I've made the following changes: 1. Resolved merge conflicts
2. Changed default behavior
Files changed:
CI Status: ✅ All checks passingThe PR is now ready for review. 🤖 Generated with Claude Code |
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
Now working session is ended, feel free to review and add any feedback on the solution draft. |
Summary
Add logging of GitHub API rate limit usage at key points during solve command execution to help identify expensive operations that consume the most API limits.
github-rate-limit-logger.lib.mjsmodule for reusable rate limit tracking--github-rate-limits-loggingflag (disabled by default, use when debugging API usage)experiments/test-github-rate-limit-logger.mjsExample Output
When enabled with
--github-rate-limits-logging:How to Enable
The rate limit logging is disabled by default. To enable it for debugging, use:
Test Plan
node experiments/test-github-rate-limit-logger.mjsFixes #1002
🤖 Generated with Claude Code