[playwright-browser-tunnel] Add advanced logging#5597
Merged
TheLarkInn merged 3 commits intomainfrom Feb 4, 2026
Merged
Conversation
TheLarkInn
requested review from
apostolisms,
dmichon-msft,
iclanton and
octogonz
as code owners
dmichon-msft
approved these changes
Feb 4, 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 PR introduces some advanced logging on both the browser tunnel and the tunneledBrowserConnection endpoints so we can have better close codes for websockets, and investigate timeouts, connection stalls, and browser tunnel crashes better.
We also were not passing in proper
ws.close()codes from our own connections so everything would log as 1006 Abnormal Closure. Passing in proper codes (where relevant) tows.close()calls.Also minor bumping the extension as it will need to be published from this change pushed.