Fix command runner timeout issue#4082
Fix command runner timeout issue#4082richardhjtan wants to merge 1 commit intocs-9945-submission-bot-open-a-github-prfrom
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 92ca85b4c7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| opts: args.puppeteerTimeoutMs | ||
| ? { timeoutMs: args.puppeteerTimeoutMs } | ||
| : undefined, |
There was a problem hiding this comment.
Forward the Puppeteer timeout to the prerender service
Setting opts.timeoutMs here does not currently change runtime behavior because the downstream proxy path drops it: packages/realm-server/prerender/remote-prerenderer.ts runCommand() only forwards { realm, auth, command, commandInput }, and packages/realm-server/prerender/prerender-app.ts /run-command also calls prerenderer.runCommand(...) without opts. In the save-submission flow this means the command still runs with the default 30s render timeout, so large submissions can continue to fail even though puppeteerTimeoutMs is set to 280000.
Useful? React with 👍 / 👎.
Preview deployments |
Host Test Results 1 files ±0 1 suites ±0 1h 30m 53s ⏱️ - 5m 36s For more details on these errors, see this check. Results for commit 92ca85b. ± Comparison against base commit 36bd710. |
Root cause fixed: create-submission was saving a large SubmissionCard (with all file contents) synchronously inside the 30-second Puppeteer timeout window. The "temporary" doNotWaitForPersist fix was a race condition — the page could be released before the background save finished.
Files changed: