Skip to content

fix(cli): give a local Chrome 30 s to start #16

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.

Sign up for GitHub

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

Merged
Madraka merged 1 commit into from
Oct 20, 2026
Merged

fix(cli): give a local Chrome 30 s to start #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/chrome-start-timeout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@cloudhal/cli": patch
---

`cloudhal render` and the MCP `render_page` tool give a local Chrome 30 seconds to start instead of 10. A cold start on a busy machine or CI runner could exceed 10 seconds and fail with "Chrome did not start".
3 changes: 2 additions & 1 deletion packages/cli/src/render-chrome.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,8 @@ export function chromeRenderer(
);
const endpoint = new Promise<string>((resolve, reject) => {
let err = "";
const timer = setTimeout(() => reject(new Error("Chrome did not start")), 10_000);
// A cold start on a busy CI runner can take well over 10 s; a warm one is under a second.
const timer = setTimeout(() => reject(new Error("Chrome did not start")), 30_000);
child.stderr?.on("data", (chunk: Buffer) => {
err += chunk.toString();
const m = /DevTools listening on (ws:\/\/\S+)/.exec(err);
Expand Down
Loading