fix: retry and sleep inmprovements - #212
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (8)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughChangesRetry and timing behavior
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: ⚪ Minimal · up to This change bounds retry delays, preserves download failure causes, improves retry exhaustion reporting, and makes WASM sleep cleanup safer. The covered retry and timing paths show no remaining merge-blocking risk. Sequence Diagram(s)sequenceDiagram
participant RangeDownloader
participant ExponentialBackoff
participant GraphQLClient
participant S3
RangeDownloader->>GraphQLClient: request S3 range
GraphQLClient->>S3: fetch range
S3-->>GraphQLClient: return error
GraphQLClient-->>RangeDownloader: preserve S3 error
RangeDownloader->>ExponentialBackoff: request next delay
ExponentialBackoff-->>RangeDownloader: return delay or None
RangeDownloader->>RangeDownloader: sleep before retry
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
Summary by CodeRabbit