Carsten Rohrbach

Same problem here. In my project, the error only occurs after a Hot Deployment. If I restart the server afterwards, the initialization succeeds.

Seems that for this the whole configuration needs to become spec based, for example mapped by spec reference. For backwards compatibility, the default config could just be used as template.

When can we expect support for Node >= 16.12.1 where the loader API changed? Trying to add the hook with dd-trace 1.7.0 on Node 16.13.1 outputs ``` (node:391569) DeprecationWarning: Obsolete...

Hi @rochdev it seems that the immediate exit of our service has nothing to do with the deprecation warning. It's also happening with the older Node 16.11.0 as soon as...

We found the root cause of the immediate exit: we had a circular dependency between module files. After fixing that, the server started as expected. It would be great if...

In that case, it would be nice if a `turbo` command in a package would automatically have an implicit `--filter` on that package, so that a ``` mypackage $ turbo...

@gsoltis does it mean that we have to always add `--infer-filter-root` to the turbo command? Would it be possible to set this as default via `turbo.json`? When calling at the...

We have a [Nushell](https://nushell.sh) script to log the last lines of each failed task: ```nushell #!/usr/bin/env nu def showLog [task] { $"----------------------------------------------------------------------------- # ($task.taskId): ----------------------------------------------------------------------------- (tail -n 50 $task.logFile) "...

It would also be great to use indirect measures for concurrency, like available resources (cpu, memory, custom resources). For example, we have tasks that are very lightweight, but others that...

It also would be cool, if in that case, an additional parameter would toggle turbo to output GitHub Workflow Group statements for every task. ``` ::group::{project name}:{task name} ::endgroup:: ```...