-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Add Puppeteer executable path environment variable to runloop blueprint #9073
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Keep this PR in a mergeable state → Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
2 similar comments
|
Keep this PR in a mergeable state → Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
|
Keep this PR in a mergeable state → Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
|
|
✅ Review Complete Code Review Summary |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
Documentation ReviewReviewed this PR for documentation updates. No documentation changes needed. ReasoningThis change adds
The change is purely an optimization to use system Chromium instead of letting Puppeteer download its own copy. This review was performed by Continue AI Agent |
|
🎉 This PR is included in version 1.36.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary by cubic
Set PUPPETEER_EXECUTABLE_PATH to /usr/bin/chromium in the runloop blueprint launch commands so Puppeteer uses the system Chromium. This prevents Puppeteer downloads and avoids launch failures under Xvfb.
Written for commit 4905bd5. Summary will update automatically on new commits.