Skip to content
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

Prevent fromPromise from swallowing errors (#334) #339

Merged
merged 4 commits into from
Oct 27, 2018
Merged

Conversation

karthikiyengar
Copy link
Collaborator

This PR resolves #334

We still need to figure out how to test for this particular behaviour, since we need to test against an UnhandledPromiseRejection. Related: tape-testing/tape#208

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling ea104e0 on issue-334 into f7641f3 on master.

@coveralls
Copy link

coveralls commented Oct 27, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 1d8d792 on issue-334 into 1e7914e on master.

Copy link
Owner

@evilsoft evilsoft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to put coverage around Computational Crashes, that is how this slipped through.
For now tho, peeps are broken on 0.10.2 and we need to change our forking scheme to be able to allow for Crash detection.

I am okay with this going out and us adding the coverage before any other work is done on Async.

image

@evilsoft evilsoft merged commit 0317dfc into master Oct 27, 2018
@evilsoft evilsoft deleted the issue-334 branch October 27, 2018 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Async.fromPromise subsequent flow swallow errors
3 participants