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

fix: handle code-less errors more carefully in exec #554

Merged
merged 1 commit into from Nov 17, 2016

Conversation

nfischer
Copy link
Member

If an error exists, but has no error code, it defaults to 1 (a common code for
most Unix commands). Tests have been omitted since this is an edge case that is
difficult to reproduce.

Fixes #536

If an error exists, but has no error code, it defaults to 1 (a common code for
most Unix commands). Tests have been omitted since this is an edge case that is
difficult to reproduce.

Fixes #536
@nfischer nfischer added the fix Bug/defect, or a fix for such a problem label Nov 12, 2016
@nfischer nfischer added this to the v0.7.x milestone Nov 12, 2016
@nfischer
Copy link
Member Author

@freitagbr ready for review

@freitagbr
Copy link
Contributor

Sure, this should work. It does seem weird that an error form child.exec would not have a code, so maybe we need to look into this further. It might even be a bug in node itself.

@nfischer
Copy link
Member Author

@freitagbr I think it is a node bug. Even if it is though, we still need to support older node platforms, so it's probably worth it to leave it in here.

@nfischer
Copy link
Member Author

@freitagbr LGTY?

@freitagbr
Copy link
Contributor

Yes, LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix Bug/defect, or a fix for such a problem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants