-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: reject contentTracing.stopRecording on failure #26608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Interesting crash on this one:
|
oh, crap, the promise was |
Release Notes Persisted
|
/trop run backport |
The backport process for this PR has been manually initiated, here we go! :D |
I have automatically backported this PR to "11-x-y", please check out #26655 |
I have automatically backported this PR to "12-x-y", please check out #26656 |
Description of Change
Fixes #26607. I'm not sure this catches all situations in which the
FileEndpoint's callback isn't called, but it catches a major one!
Checklist
npm test
passesRelease Notes
Notes: Fixed
contentTracing.stopRecording()
not rejecting when there is no trace in progress.