Closed m-Peter closed 4 weeks ago
The changes involve increasing the limits for batch requests and responses in the server configuration and modifying a test case to validate the new limits. The batchRequestLimit
was raised from 5 to 50, and the batchResponseMaxSize
was increased from 5 MB to 10 MB. Additionally, a test case was updated to check for errors when exceeding the new request limit.
Files | Change Summary |
---|---|
api/server.go , tests/web3js/... |
Increased batchRequestLimit from 5 to 50 and batchResponseMaxSize from 5 MB to 10 MB. Updated test logic to validate behavior when exceeding the new request limit. |
sequenceDiagram
participant Client
participant Server
Client->>Server: Send batch request (up to 50 requests)
Server-->>Client: Process requests and send response (up to 10 MB)
Client->>Server: Send batch request (more than 50 requests)
Server-->>Client: Return error (exceeds limit)
🐇
In the meadow where requests do flow,
Batches now can grow and grow!
Fifty hops, a joyful spree,
Responses large, oh what glee!
With every leap, we test and play,
A brighter path, come what may!
🌼
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?
Description
The Flow Wallet Team mentioned that they do 25+ calls in a batch request.
For contributor use:
master
branchFiles changed
in the Github PR explorerSummary by CodeRabbit
New Features
Bug Fixes