#Local traces

1 messages · Page 1 of 1 (latest)

hushed cove
#

Hi! These traces /root/.cache/dagger/dagger-0.18.5 session --label dagger.io/sdk.name:python --label dagger.io/sdk.version:0.18.5 are mostly irrelevant and quite annoying, except when calling Dagger’s native LLM because they include both the prompt and the bot’s response. This is the code in my app:

`# Configure basic logging with INFO level
logging.basicConfig(level=logging.INFO)

Create a logger instance for this module

logger = logging.getLogger(name)`

Is there a way to remove the system traces and keep only the useful stuff?

PS: The last trace in the image shows my user profile and it was a test for dagger -m github.com/shykes/daggerverse/hello@v0.3.0 call hello but I have no idea why my profile image is shown there and not with all the other traces. Also no idea why the first trace is always yellow as long as the app is running in Docker.

hybrid zodiac
#

@hushed cove I think this is because your engine was started with the DAGGER_CLOUD_TOKEN. Would you mind trying the following?

  1. Remove your engine container $(docker rm -fv dagger-engine-v0.18.5)
  2. unset DAGGER_CLOUD_TOKEN from your env
  3. perform a dagger login to make sure you're logged in to your org
#

that should fix it