turborepo: Watch mode show limited error message for 'invalid task configuration'
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
n/a
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
1.13.3-canary.3
Describe the Bug
When I run turbo run dev I am getting a different error message then when I run turbo watch dev. The version of shown when using run-command is more helpful
Expected Behavior
When running turbo run dev I am currently getting:
pnpm exec turbo run dev
× invalid task configuration
Error: × You have 20 persistent tasks but `turbo` is configured for concurrency of 10. Set --concurrency to at least 21
while when running turbo watch dev only a part of the above message is outputted by the command, see:
pnpm exec turbo watch dev
× invalid task configuration
To Reproduce
You should be able to reproduce by trying to lowering the turbo watch dev --concurrency=1
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 23 (17 by maintainers)
Yes, the problem is still occurring, but this issue is originally for a completely different problem, so I’d prefer that we open a new issue with a more relevant title, so people can easily search and find it.
I’m also seeing the
failed to connect to daemonerror in turborepo 2.0.1 and 2.0.2-canary.0. I don’t have a lot of packages.When this error occurs, there is only one new line in the daemon logs:
My env:
Should I start a separate thread, I wonder?
@NicholasLYang I can confirm the original issue is resolved in 1.3.3 only I haven’t been to get
watchworking:Hi, could you try running
turbo daemon cleanand see if that fixes anything?We are receiving this as well in
"turbo": "2.0.3",. It’s not ideal, but when this happens run:px axu | grep turboand find the duplicate process ID then kill it, i.e.kill {id}