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
chore: fix dangling promise in npm install #36379
Conversation
💖 Thanks for opening this pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should update your pull request title to start with a semantic prefix. Examples of commit messages with semantic prefixes:
Things that will help get your PR across the finish line:
We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can. |
Co-authored-by: Black-Hole <158blackhole@gmail.com>
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
Congrats on merging your first pull request! 🎉🎉🎉 |
No Release Notes |
I have automatically backported this PR to "22-x-y", please check out #36398 |
I have automatically backported this PR to "21-x-y", please check out #36399 |
I have automatically backported this PR to "20-x-y", please check out #36400 |
* Fix dangling promise introduced in electron#33979 * fix reject in callback * simplify code Co-authored-by: Black-Hole <158blackhole@gmail.com> Co-authored-by: Black-Hole <158blackhole@gmail.com>
Description of Change
Fix an unresolved promise introduced in #33979, where the
resolve
is never called.This problem was not observable because there's no variable holding reference to the promise, so V8 will correctly GC it. But the code logic still has problem.
Checklist
npm test
passesRelease Notes
Notes: no-notes