-
Notifications
You must be signed in to change notification settings - Fork 37
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
feat: tx queue for unordered txs requests #48
Conversation
Warning Rate limit exceeded@beer-1 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 50 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. 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. WalkthroughThe recent changes enhance the configuration and error handling of the EVM and JSON-RPC backend, improving transaction management and cache flexibility. Notable adjustments include dynamic cache size determination in the EVM indexer, the introduction of a transaction queue in the JSON-RPC backend, and enhanced error handling throughout. These updates collectively improve the robustness and configurability of the system, allowing for better resource management and operational performance. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Backend
participant CacheStore
participant Keeper
User->>Backend: Send transaction
Backend->>CacheStore: Lock access
CacheStore->>Backend: Validate and queue transaction
Backend->>Keeper: Retrieve configuration
Keeper-->>Backend: Return EVM configuration
Backend-->>User: Confirm transaction status
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 Configuration File (
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #48 +/- ##
==========================================
- Coverage 26.53% 26.35% -0.19%
==========================================
Files 111 111
Lines 11770 11855 +85
==========================================
+ Hits 3123 3124 +1
- Misses 8202 8286 +84
Partials 445 445
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Foundry script is sending txs in unordered, to handle these request we keep tx queue.
Closes: #XXXX
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
in the type prefix if API or client breaking changeReviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
Summary by CodeRabbit
New Features
Bug Fixes
Style
Chores