[test] Show decoded binary WebSocket messages in traces#91308
Merged
eps1lon merged 1 commit intoMar 13, 2026
Merged
Conversation
This was referenced Mar 13, 2026
Member
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Mar 13, 2026
unstubbable
approved these changes
Mar 13, 2026
Base automatically changed from
sebbie/03-12-_test_more_robust_instant-navs-devtools_actions_and_assertions
to
canary
March 13, 2026 16:26
Member
Author
Merge activity
|
eps1lon
force-pushed
the
sebbie/03-13-_test_show_decoded_binary_websocket_messages_in_traces
branch
from
45db1fd to
d6ef9fb
Compare
eps1lon
deleted the
sebbie/03-13-_test_show_decoded_binary_websocket_messages_in_traces
branch
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Follow-up to #91266
Showing the Buffer is just noise. Now we print it decoded which shows us the Flight data from the debug channel:
I switched to just evaluating the string. It'll still show up in traces but won't show up in browser logs i.e. CI logs. Felt to spammy.