Repository navigation
Say why a navigation wait timed out - #60
Merged
Merged
Conversation
…ght and failed A 30 s stall in CI said only that 30 s passed. GotoAsync, an action's navigation wait and WaitForLoadState/WaitForUrl now append the page state: URL, readyState, lifecycle events reached, the requests still in flight with their age, the last failed or 4xx/5xx ones, and the last script error. Pages enable the Network domain on creation to keep that (URLs and counts only). The script is bounded to 2 s. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
A slow runner hit the 300 ms timeout inside GotoAsync itself. Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
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
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.
Why
A navigation timeout in CI said only that 30 s passed ("Timed out after 30s waiting for the URL to match ...", "A navigation the action started did not finish loading within 30 seconds"). Two demo/edge journey runs stalled this way at the same moment and there was nothing to tell a slow origin from a hung renderer.
What
GotoAsync, an action's navigation wait andWaitForLoadState/WaitForUrlappend aPage state when it gave up:block to theirTimeoutException:document.readyStatePages now enable the
Networkdomain when created so this is known (URLs and counts only, no headers or bodies;NetworkRecordingstays the opt-in for lists and HAR). The state script is bounded to two seconds, so a hung renderer is reported as not answering and never delays the timeout. Recorded in DECISIONS.md.Verification
Full suite passes (497). Two new live tests (a hanging image in flight; a 404 image after load). Mutated
StateAsyncto drop the request lines and both new tests failed; restored.🤖 Generated with Claude Code