chore: optimize for concurrency#302
Conversation
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe test for NEP-245 deposit resolve gas now always runs NEP-245 Gas Test Concurrency
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
tests/src/tests/defuse/tokens/nep245/mt_deposit_resolve_gas.rs (1)
25-25: 🩺 Stability & Availability | 🔵 Trivial | ⚡ Quick winBound the gas-test fan-out.
try_join_alllaunches all 1..=max_deposited_count runs at once; switch to bounded concurrency (for example,buffer_unordered) so this test doesn’t overwhelm CI/sandbox resources when it reaches 50–200 transaction-heavy cases.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@tests/src/tests/defuse/tokens/nep245/mt_deposit_resolve_gas.rs` at line 25, The gas test fan-out in the NEP245 `mt_deposit_resolve_gas` test is unbounded because `try_join_all` starts every case at once, which can overwhelm CI and sandbox resources. Replace the `try_join_all`-based execution with bounded concurrency in the test harness (for example, using a `buffer_unordered`-style stream) so only a limited number of transaction-heavy cases run simultaneously, and keep the change localized to the `mt_deposit_resolve_gas` test logic.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@tests/src/tests/defuse/tokens/nep245/mt_deposit_resolve_gas.rs`:
- Line 25: The gas test fan-out in the NEP245 `mt_deposit_resolve_gas` test is
unbounded because `try_join_all` starts every case at once, which can overwhelm
CI and sandbox resources. Replace the `try_join_all`-based execution with
bounded concurrency in the test harness (for example, using a
`buffer_unordered`-style stream) so only a limited number of transaction-heavy
cases run simultaneously, and keep the change localized to the
`mt_deposit_resolve_gas` test logic.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: b868d0ac-d40b-4294-9a48-a58908a277f9
📒 Files selected for processing (1)
tests/src/tests/defuse/tokens/nep245/mt_deposit_resolve_gas.rs
Summary by CodeRabbit