Let the deploy's anonymous probe pass through the reputation gate - #115
Conversation
The post-deploy check curls one anonymous classification from the hosted runner. The free-traffic reputation gate can refuse a runner's IP with 403 proxy_requires_payment, which is the Worker answering with its own gate, not a broken deploy; the last two deploys were marked failed by it, and `curl --fail` discarded the body that would have said so. The probe now prints the status and body, passes with a notice on the gate's own 403, still requires "spam" on a 200, and fails on anything else. The funded end-to-end step that followed it runs again. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe deploy workflow now captures and prints the live-check response. It accepts HTTP 200 with the ChangesDeploy probe handling
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The deploy probe now reports its response and permits the expected reputation-gate response without masking other failures. No merge-blocking risk is identified. 🚥 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 |
The post-deploy "Check what is live" step curls one anonymous classification from the hosted runner. The free-traffic reputation gate can refuse a runner's IP with
403 proxy_requires_payment— the Worker answering with its own gate, not a broken deploy. The deploys for #113 and #114 were marked failed by exactly this, andcurl --faildiscarded the response body that would have shown it.The step now:
::notice::when the answer is the gate's own403 proxy_requires_payment;spamon a 200, and fails on any other status.The funded "Check multidimensional classification end to end" step, skipped after the failure, runs again.
🤖 Generated with Claude Code
Summary by CodeRabbit