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

Windows child process spawn, exec, execFile hangs #503

Closed
1 of 4 tasks
AndyOGo opened this issue Jun 26, 2018 · 3 comments · Fixed by #553
Closed
1 of 4 tasks

Windows child process spawn, exec, execFile hangs #503

AndyOGo opened this issue Jun 26, 2018 · 3 comments · Fixed by #553
Assignees
Milestone

Comments

@AndyOGo
Copy link

AndyOGo commented Jun 26, 2018

Are you reporting a bug or a feature?

  • Bug
  • Feature

Expected Behavior

All processes spawned, forked, execed or or execFiled should properly exit at all platforms, especially Windows, MacOS and UNIX-systems.

Actual Behavior

  • No child process exits properly at windows
  • Logging does not work in windows

Steps to Reproduce the Problem

  1. npm run release

Known Issues

@AndyOGo
Copy link
Author

AndyOGo commented Jun 26, 2018

Yeah kill them all...
https://github.com/sindresorhus/fkill-cli

@AndyOGo
Copy link
Author

AndyOGo commented Jun 26, 2018

@AndyOGo
Copy link
Author

AndyOGo commented Jul 3, 2018

sindresorhus/execa#142

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants