-
Notifications
You must be signed in to change notification settings - Fork 16.2k
feat: promisify contentTracing.getTraceBufferUsage() #16600
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
320fe26
to
8c5730a
Compare
11a4e08
to
ccf5b58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
}) | ||
} | ||
}, | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
ccf5b58
to
fa6fa7e
Compare
fa6fa7e
to
89c1685
Compare
Release Notes Persisted
|
/trop run backport-to 5-0-x |
The backport process for this PR has been manually initiated, |
I was unable to backport this PR to "5-0-x" cleanly; |
sadness |
Description of Change
Promisify
contentTracing.getTraceBufferUsage()
.NB: this PR required backwards-incompatible changes and thus cannot be backported to
5-0-x
.cc @ckerr @deepak1556
Checklist
npm test
passesRelease Notes
Notes: Converted
contentTracing.getTraceBufferUsage()
to return a Promise instead of taking a callback.