logger noise that should be debug, and not being able to turn wandb logging off
See original GitHub issueJust rebased transformers, needed to update wandb
and started getting this when running hf trainer:
2021-01-07 18:46:19 | INFO | wandb.sdk.internal.internal | Internal process exited
2021-01-07 18:46:19 | INFO | wandb.sdk.internal.internal | Internal process exited
-
why is this info and not debug? I can’t see what useful information this adds to the user of the hosting application. Turning this to DEBUG would be awesome. thanks.
-
export WANDB_CONSOLE=off
didn’t shut it off the docs suggest https://docs.wandb.ai/library/environment-variables -
Would it be possible to add:
WANDB=DISABLED
env var or something like that similar to how COMET_MODE=DISABLED
does it? which would mean don’t load the module at all even if it’s available and API KEY is configured.
When I work on something it makes things difficult when modules that don’t participate in the development process start logging their stuff. I don’t use wandb most of the time, but the fact that I have it installed keeps on running it.
Thank you very much.
For now going to uninstall wandb
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (5 by maintainers)
Top GitHub Comments
Awesome - thank you for that tip. I can confirm that before the change, the
internal process exited
log would be emitted. After the change, wandb’s normal output can be observed.Sorry, I misspoke. It’s
WANDB_DISABLED=true
, I should have read the code that I linked to 🙃