-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Bug?]: Process hangs with parallel-prettier #4354
Comments
I'm guessing this is the same issue as #4157, can you test with Node.js v16.14 or v17.4? |
@merceyz Thank you for the response. I tested on v16.14 but still got no luck: System:
OS: macOS 12.2.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Binaries:
Node: 16.14.2 - /private/var/folders/28/yhtzwdv94rg8cf93ncdjc02h0000gr/T/xfs-79ab10bc/node
Yarn: 3.2.0 - /private/var/folders/28/yhtzwdv94rg8cf93ncdjc02h0000gr/T/xfs-79ab10bc/yarn
npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm |
@merceyz The issue still exists, can you take another look? |
This comment was marked as outdated.
This comment was marked as outdated.
I attempted to reproduce the issue, but didn't have any luck. Are you able to provide a repository that allows for a minimal reproduction of the behavior? |
I can reproduce with the following commands docker run --rm -it node:16.15.0 bash
mkdir foo
cd foo
corepack enable
corepack prepare yarn@3.2.1 --activate
yarn init
yarn add @mixer/parallel-prettier@2.0.1 concurrently@7.0.0
yarn pprettier --write ./package.json |
Interesting discovery... after running |
Self-service
Describe the bug
We use the dependency
@mixer/parallel-prettier
to prettify our huge codebase in parallel. However, formatting process hangs if the dependency co-exists with some other dependencies(i.e.concurrently
). I looked into the source code, it looks normal, other than it usescluster
module.To reproduce
Playground
Environment
System: OS: macOS 12.2.1 CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz Binaries: Node: 14.19.1 - /private/var/folders/28/yhtzwdv94rg8cf93ncdjc02h0000gr/T/xfs-2f0d5096/node Yarn: 3.2.0 - /private/var/folders/28/yhtzwdv94rg8cf93ncdjc02h0000gr/T/xfs-2f0d5096/yarn npm: 6.14.16 - ~/.nvm/versions/node/v14.19.1/bin/npm
Additional context
I did a search in our other dependencies, it seems like many other dependencies will cause the same issue like
concurrently
:I don't think they share a lot commonalities.
The text was updated successfully, but these errors were encountered: