Fix BenchmarkConnector call to console.warning - #588
Merged
Merged
Conversation
Opening any remote workload outside the harness threw a TypeError on the first stray message instead of logging it. Note that I didn't rebuild the existing remote workloads. I checked the others and it looks like they show a bit diff in the bundle, so I chose to leave them for now. The next rebuild will take this up.
✅ Deploy Preview for webkit-speedometer-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
camillobruni
approved these changes
Sep 22, 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
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.
Opening any remote workload outside the harness threw a TypeError on the first stray message instead of logging it.
Note that I didn't rebuild the existing remote workloads. I checked the others and it looks like they show a bit diff in the bundle, so I chose to leave them for now. The next rebuild will take this up.
I noticed this while working on a new remote workload for pdf.js.