Turborepo does not finalize and process files in WSL

[andrehrferreira]

Verify canary release

• I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

https://github.com/cmmvio/cmmv-blog

Which canary version will you have in your reproduction?

2.4.4

Expected behavior

When pressing request to end the process in the console, the shift is ended instead of ignoring SIGKILL

Actual behavior

Hi!

I recently switched from Lerna to Turbo and decided to test it with a simple blog project structured with a few packages and apps. Everything is set up correctly and working in general.

Just to clarify my environment:

• OS: Windows 10
• Node.js: v20
• WSL: WSL 2 with Ubuntu 20.04.6 LTS
• Package manager: pnpm

Turbo version: latest (via pnpm install turbo)

After running pnpm dev, which triggers turbo run dev, I noticed that a turbo process is spawned and becomes visible in the Windows Task Manager.

The problem is: when I press CTRL+C to stop the dev process, the Turbo process does not exit. It seems to ignore the WSL signal or is somehow stuck.

Trying to run any pnpm command results in a  ERR_PNPM_EACCES  EACCES: permission denied, rename

The process seems to be locking files inside node_modules, especially:

node_modules/turbo-linux-64/bin/turbo

I’m completely unable to remove node_modules or reinstall until I reboot the entire machine

I’ve tried terminating the Turbo process from within WSL, but it remains active until killed from the Windows Task Manager (and even that sometimes fails)

I'm still new to Turbo, so I’m not sure if there’s a workaround or fix for this yet — but this issue makes the DX very frustrating in WSL environments. Is there any known solution for this behavior?

Thanks in advance, and happy to provide logs or help debug if needed!

To Reproduce

No special behavior just install turbo on WSL with Ubuntu

Additional context

No response

[anthonyshew]

If you turn the daemon off, do you still see the same behavior?

https://turbo.build/repo/docs/reference/configuration#daemon

[andrehrferreira]

I did some tests, when I turn off the daemon the problem stops, as a palliative it's ok, but I believe that this type of behavior wasn't supposed to happen, right? Because even if you put a service or daemon as you prefer, in theory it should respect my command in the WSL console to finish, but it simply hangs there and there's apparently nothing to do.

[anthonyshew]

Correct, I was taking an informed guess that the daemon would be a part of this based on my memory of a few prior issues. Thank you for confirming.

Turning off the daemon is a viable workaround until we have a solve. Turborepo will continue to work as expected with a slight performance degradation (only at startup of invocation, scales with repository size).