Open ixxie opened 20 hours ago
Thanks for writing out your use case; indeed that's a big ask and when I thought about it before, I kept it out of scope because I didn't have a compelling enough need, but I'm willing to think this through.
Syntactically, we'd add a --parallel
to the CLI and composite.parallel
to the config. We'd also label lines with the task name that started them + color (or something like that).
But the actual mechanism requires us to know:
keep_going
implied? Or maybe if one goes down they all go down (unless you're explicit about which keep running)?
Is it possible to execute multiple long-running tasks concurrently, feeding
stdout
andstderr
into the main process?Our usecase is running a variety of services in dev mode in tandem, during development. We currently use concurrently.js for this, a NodeJS based tool. The challenge with this tool is that it doesn't play well with Uvicorn's HMR functionality.
I realize this is a big ask, so I wouldn't be surprised if you decide to scope this out of the library, but it is a very important usecase for workspace task running in my opinion.