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

child_concurrency configuration not used #6118

Open
victornoel opened this issue Jul 18, 2018 · 2 comments
Open

child_concurrency configuration not used #6118

victornoel opened this issue Jul 18, 2018 · 2 comments
Assignees
Labels

Comments

@victornoel
Copy link
Contributor

There is a child_concurrency configuration (see https://yarnpkg.com/en/docs/envvars#child_concurrency- and https://yarnpkg.com/en/docs/yarnrc#child-concurrency-) but it is apparently not taken into account.

See https://github.com/yarnpkg/yarn/blob/2f0eb8eace4c19c5e4606176371782c60bc7e0e7/src/util/child.js where the constant is used instead of the configuration.

I'm having problems either with #1874 or #3728 and this is preventing me from working around it I think…

@ghost ghost assigned arcanis Jul 18, 2018
@ghost ghost added the triaged label Jul 18, 2018
@victornoel
Copy link
Contributor Author

@arcanis and will this be solved in 2019? ;)

@quitedensepoint
Copy link

Yeah, this is pretty annoying. I run into problems with node-gyp via yarn every few days because of #1874 and can't work around it with CHILD_CONCURRENCY because it doesn't do anything per this issue.

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

No branches or pull requests

3 participants