Repository navigation
Address CodeRabbit review: timeout, session-id guard, CI hardening - #2
Conversation
- api(): bound fetch with AbortController (FIRECRAWL_HTTP_TIMEOUT_MS, default 60s) so a stalled call can't block the single response - browser.launch: validate session.id (not just cdpUrl) so we never report success without a closable session - ci.yml: persist-credentials: false on checkout - test: add no-session-id guard case (10 tests total) Skipped CodeRabbit's SHA-pinning suggestion: CI is hermetic (no secrets/deploy), so the maintenance cost outweighs the benefit for this repo. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe ChangesPlugin HTTP Timeout and Session ID Validation
CI Credential Persistence Hardening
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Applies the actionable findings from the CodeRabbit review (PR #1).
api()timeout —AbortControllerbounds every Firecrawl call (FIRECRAWL_HTTP_TIMEOUT_MS, default 60s), so a stalled request can't block the plugin's single response.session.idguard —browser.launchnow validatessession.idas well ascdpUrl; prevents reporting success when the session can't be closed later (leak).persist-credentials: falseon checkout.Deliberately skipped: SHA-pinning the GitHub Actions (
@v4→ commit SHA). CI is hermetic (no secrets, no deploy, no publish), so the maintenance cost outweighs the supply-chain benefit here.Verified:
node --test(10/10) + live launch/close against the real Firecrawl API.🤖 Generated with Claude Code
Summary by CodeRabbit