Use Selenium’s default session request timeout - #55
Merged
Merged
Conversation
The 30-second cutoff rejected a Codespaces browser that started after 31.7 seconds. Let Selenium's own deadline accommodate slow starts instead of adding warm-up or retry machinery. Provider qualification remains tracked in firstdraft/firstdraft#729.
raghubetina
force-pushed
the
codex/selenium-default-session-timeout
branch
from
September 24, 2026 15:52
83ffe99 to
7be76f3
Compare
raghubetina
marked this pull request as ready for review
September 24, 2026 16:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove Drawing Board’s 30-second Selenium session-request override to follow the approved upstream-default behavior. The server queue default is 300 seconds; generated applications retain a separate 60-second Ruby HTTP read timeout. No warm-up scripts or retries are added.
script/check, Compose validation and final-head hosted contract CI pass. Claude Opus 5.5 independently reviewed this companion and Core #119; the timeout explanation is corrected. The observed Codespaces failure and remaining provider qualification stay under Service #729. New root-compiled apps require the separate Service Core adoption.