fix(turborepo): Persistent tasks in watch mode

[NicholasLYang]

Description

Fixing persistent tasks in watch mode. I accidentally reversed the dependency relation which created a circular dependency which in turn caused a deadlock.

Testing Instructions

Try out turbo watch dev in create turbo

Closes TURBO-3020

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
examples-nonmonorepo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 7, 2024 10:46pm
rust-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 7, 2024 10:46pm

8 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
examples-basic-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-designsystem-docs	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-gatsby-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-kitchensink-blog	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-native-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-svelte-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-tailwind-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm
examples-vite-web	⬜️ Ignored (Inspect)			May 7, 2024 10:46pm

[NicholasLYang]

• fix(turborepo): Persistent tasks in watch mode #8107 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @NicholasLYang and the rest of your teammates on Graphite

[github-actions]

🟢 Turbopack Benchmark CI successful 🟢

Thanks

[github-actions]

🟢 CI successful 🟢

Thanks

[orjan]

Will this fix make sure that a persistent task is restarted when a dependency has been changed?

[NicholasLYang]

@orjan, no, the assumption is that persistent tasks are self healing, i.e. if a dependency changes, the persistent task will figure that out without having to be re-run. Persistent tasks are only re-run if we need to do a full rediscovery, which happens if the underlying turbo graph changes.

[orjan]

@orjan, no, the assumption is that persistent tasks are self healing, i.e. if a dependency changes, the persistent task will figure that out without having to be re-run. Persistent tasks are only re-run if we need to do a full rediscovery, which happens if the underlying turbo graph changes.

Thanks for the explanation, it explains why I wasn't able restart the task here:
#8095