fastbrowser.setup: skip survives the requested-host-absent wording - #308
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
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 (2)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe setup flow now recognizes fast-browser’s requested-host-missing error. A test verifies that non-interactive setup skips with the existing no-host detail. ChangesFast-browser no-host handling
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The update correctly skips only recognized no-host failures in non-interactive setup while preserving other errors. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
The v2.9.0 rehearsal (run 35233591900) dead-ended in the CI clean-room: fast-browser now says "Requested claude host was not detected" where it used to say "Detected hosts: none", so the honest-skip match in fastbrowser.setup degraded to the loud failure it was designed to degrade to, and Install stopped at fastbrowser.setup on a runner with no Claude host.
One-line fix: broaden NO_HOST_STDERR to match both spellings (
Requested \S+ host was not detected). Test-first: new case with the 0.1.1 wording was RED, now GREEN; the interactive path stays loud and a non-host failure stays failed (existing cases untouched, 102/102 pass, tsc clean).Release-blocking for v2.9.0: the rehearsal cannot pass without it.
🤖 Generated with Claude Code
Summary by CodeRabbit