-
Notifications
You must be signed in to change notification settings - Fork 39
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
Release for Python 3.11 and 3.12 #481
Conversation
Warning Rate Limit Exceeded@thunderbiscuit has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 13 seconds before requesting another review. 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. WalkthroughThe recent updates focus on modernizing the development environment and improving compatibility across the board. Key changes include updating Java and Kotlin versions to enhance JVM and Android builds, upgrading Gradle for better build tooling, and introducing Rust and Python updates for broader development support. Additionally, there's a significant focus on error handling improvements, particularly around fee rate calculations in the Bitcoin development kit, alongside structural changes to build and test configurations to streamline development processes. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
ACK My only question is since the PR touches Python+JVM+Android (and I see this follow on PR about JVM+Android #480 ) I was wondering how you were going to approach the commit history? Since it would be nice to have the Python related ones in one PR and all the JVM+Android ones in the other PR (so like separate the PR's starting with the commit related to |
Just trying to see if it passes the test workflows...