fix: update reverse_proxy.py to return correct status code for upstream request timeout - #210
Conversation
…eam request timeout
|
Claude finished @lhoupert's task in 1m 21s —— View job Review: reverse_proxy.py upstream timeout/connect-error handling
✅ No blocking issues — safe to merge. The exception ordering is safe: Non-blocking observations:
Simplify (ponytail) Nothing to cut — the diff is a minimal try/except with two branches, no unnecessary abstraction. 💰 Estimated review cost: $0.30 · 1m21s · 15 turns |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #210 +/- ##
==========================================
+ Coverage 89.65% 89.68% +0.03%
==========================================
Files 30 30
Lines 1343 1348 +5
Branches 182 182
==========================================
+ Hits 1204 1209 +5
Misses 97 97
Partials 42 42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
The 504/502 branches added for upstream transport failures had no test coverage, failing codecov/patch and codecov/project. Drive them via an httpx.MockTransport that raises, and give the mock request helper a receive channel so proxy_request can stream its body. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ca7a1ab to
64a9120
Compare
closes #211