Rich failure logging#36
Merged
JornC merged 6 commits intoaerius:mainfrom Apr 14, 2026
Merged
Conversation
JornC
force-pushed
the
rich-failure-logging
branch
2 times, most recently
from
c8dc5ee to
46fc568
Compare
JornC
force-pushed
the
rich-failure-logging
branch
from
46fc568 to
a50a999
Compare
BertScholten
reviewed
Apr 2, 2026
…es() Disabled by default to avoid unnecessary CDP overhead. When off, network events are not subscribed to and no tracker is allocated.
BertScholten
reviewed
Apr 3, 2026
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
2 participants
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.
This adds failure diagnostics backward compatibly: when failures occur, it dumps network diagnostics to LOG, including URL, error text, status code, and response body.
Re: the test, it's basically fake and meant to be run manually, won't ever work in a CI environment and thus will always succeed