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 (release.js): Protect against EPIPE bombs from npmjs (closes #645). #650

Merged
merged 1 commit into from Mar 15, 2016

Conversation

marcoscaceres
Copy link
Member

  • Adds epipebomb package, which swallows EPIPE errors.
  • Adds a default timeout to toExecPromise, and the ability to override it.
  • Increases timeout for npm publish.

@@ -214,4 +222,4 @@ async.task(function * () {
() => process.exit(0)
).catch(
err => console.error(err)
);
);
Copy link
Contributor

Choose a reason for hiding this comment

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

No newline at end of file?

 * Adds epipebomb package, which swallows EPIPE errors.
 * Adds a default timeout to `toExecPromise`, and the ability to override it.
 * Increases timeout for npm publish.
@marcoscaceres
Copy link
Member Author

my editor decided to eat new lines at the end of docs :/

@halindrome
Copy link
Contributor

huh. ok. LGTM. no real way for me to test it except to attempt a node tools/release.js when we are ready

marcoscaceres pushed a commit that referenced this pull request Mar 15, 2016
Fix (release.js): Protect against EPIPE bombs from npmjs (closes #645).
@marcoscaceres marcoscaceres merged commit b084305 into develop Mar 15, 2016
@marcoscaceres
Copy link
Member Author

@halindrome that's how we roll, "test release in release!" we are 🐮+👦z!

@marcoscaceres marcoscaceres deleted the fix_npm_publish branch March 15, 2016 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants