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)

Most upvoted comments

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 daemon error in turborepo 2.0.1 and 2.0.2-canary.0. I don’t have a lot of packages.

❯ npx turbo watch build:watch graphql:generate --filter=rights...
• Packages in scope: <redacted>
• Running build:watch, graphql:generate in 7 packages
• Remote caching disabled
  × failed to connect to daemon
  ╰─▶ server is unavailable: channel closed

When this error occurs, there is only one new line in the daemon logs:

2024-06-05T20:56:58.703710Z ERROR turborepo_lib::daemon::server: package changes stream closed: channel closed

My env:

node v18.19.1
npm v9.9.3

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 watch working:

pnpm exec turbo watch build --filter={packages/\*}
• Packages in scope: <snip>
• Running build in 36 packages
• Remote caching enabled
  × failed to connect to daemon
  ╰─▶ server is unavailable: channel closed

pnpm exec turbo daemon status
✓ daemon is running
log file: /Users/xx/Development/Projects/monorepo/.turbo/daemon/f5b0831ce8ff9a15-turbo.log.2024-04-29
uptime: 2h 4m 42s 815mss
pid file: /var/folders/1m/4921_csd7gnddqdr0smhfqjh0000gn/T/turbod/f5b0831ce8ff9a15/turbod.pid
socket file: /var/folders/1m/4921_csd7gnddqdr0smhfqjh0000gn/T/turbod/f5b0831ce8ff9a15/turbod.sock

pnpm exec turbo watch build --filter={packages/\*}
• Packages in scope: <snip>
• Running build in 36 packages
• Remote caching enabled
  × failed to connect to daemon
  ╰─▶ server is unavailable: channel closed

Hi, could you try running turbo daemon clean and 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 turbo and find the duplicate process ID then kill it, i.e. kill {id}