Adding back API timeout changes - #349
yguntur-bot wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe Snowflake client now creates a five-minute child context for request polling. When the deadline expires, polling returns a cancellation error instead of continuing indefinitely. ChangesSnowflake polling control
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to Snowflake polling now stops after five minutes rather than running indefinitely. No current merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Signed-off-by: Yaswanth Guntur <yguntur@redhat.com>
5b36629 to
ef2664e
Compare
Changes
📝 Description
What changed?
Adding back the API timeout changes which has been removed due to pod restarts happened last week
Why is this change needed?
Snowflake team has applied the patch to decrease the timeout errors and we should need to revert our old changes (#342)
Dependencies
🧪 Testing
Test Coverage
Performance Impact
🚀 Deployment
Deploy Steps
Prerequisites
Post-Deployment Monitoring
Rollback Plan
Details:
⚙️ Configuration Changes
✅ Developer Checklist