-
Notifications
You must be signed in to change notification settings - Fork 216
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
Fix unhandled promise rejections #528
Conversation
In case the installation fails, the exception is not propagated to the try-catch in `run()`, but dropped instead. We resolve this by returning their promises. Resolves #515
Makes use of definite-assignment analysis.
Codecov Report
@@ Coverage Diff @@
## v2-branch #528 +/- ##
===========================================
Coverage 100.00% 100.00%
===========================================
Files 2 2
Lines 10 10
===========================================
Hits 10 10 Continue to review full report at Codecov.
|
Falls back to the error itself, if the catch param does not have a message. Before, accessing `err.message` would print `undefined` because strings were thrown.
Some fixes were published upstream: r-lib/actions#528
When the network is slow or down, it is good to see what is going on.
Thanks! This action uses node 12, still, so made some small updates and regenerated the JS with an older typescript. |
This pull request has been automatically locked. If you believe you have found a related problem, please file a new issue and include a link to this pull request. |
While forking and refactoring this action, I discovered some issues. This is a backport to upstream of these fixes.
In case the installation fails, the exception is not propagated to the try-catch in
run()
, but dropped instead.We resolve this by returning their promises.
Resolves #515