For example, see this job: https://github.com/dagger/dagger/actions/runs/10404137513/job/28811986035?pr=8158
The job is correctly configured using a dagger token, and tracing is setup - see the top of the job. However, nested CLI calls of dagger still get this message.
We should have some way for the CLI to detect if it's nested, and if it is, disable this tracing message (it makes for more confusing logs and lots of repetition of the message). Also, it's confusing - we are tracing these (so we shouldn't set a message saying that they're not).
For example, see this job: https://github.com/dagger/dagger/actions/runs/10404137513/job/28811986035?pr=8158
The job is correctly configured using a dagger token, and tracing is setup - see the top of the job. However, nested CLI calls of dagger still get this message.
We should have some way for the CLI to detect if it's nested, and if it is, disable this tracing message (it makes for more confusing logs and lots of repetition of the message). Also, it's confusing - we are tracing these (so we shouldn't set a message saying that they're not).