Weyert de Boer

@NicholasLYang Is this IPC protocol for daemon documented somewhere?

I wished I wouldn't need to dependent on `turbowatch` or extraneous file watching to achieve this. Now I will be watching the same things twice. Once by `turbo watch` and...

Yes, I have 14 backend servers, one Rust service, and two ASP.net services, and 4 Next.js projects plus ton of packages adding up to around 80+ packages in total. I...

I am also seem to get the following message when not trying to run `persistent` tasks: ```bash × failed to connect to daemon ╰─▶ server is unavailable: channel lagged by...

Looks like the error goes away when you only watch a few packages (3-4) but fails when you try to watch all your packages (60)

Also looks like `turbo run build` now has much higher cpu usages than before. I will double check this tomorrow but it's >=70% or two `turbo` processes both sharing ~30-35%...

I did find some daemon logs: ``` 2024-04-20T22:14:29.846856Z WARN turborepo_filewatch::package_watcher: lagged behind 57389 processing file watching events 2024-04-20T22:14:46.317279Z WARN turborepo_filewatch::package_watcher: lagged behind 10745 processing file watching events 2024-04-20T22:14:46.374547Z WARN turborepo_filewatch::package_watcher:...

Thank you, for taking the time to look into it!

Sure! I only think the latest is still the `canary.3` release?

Ah I have found `.canary.4`. Probably a bit too tired last night. I will give it a shot today :)