New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLI login
command incorrectly triggers interactive prompt
#1156
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Thank you very much for reporting! We have filed a ticket for this. |
Hey @brentschroeter |
@ariG23498 this issue is still there. Experienced it while trying to init as anonymous on a kaggle kernel |
@KhushalB did you figure out a workaround on the kaggle kernel? Running into this problem now. |
@ecthompson99 setting anonymous='must' worked for me. Was not able to claim the runs from my wandb account after though. |
Same experience as @KhushalB - I can create anonymous runs but I can't claim them. Is claiming still supported somehow? |
Description
From a fresh install, attempting to log in via the command line using
wandb login <valid API key>
should succeed without requiring interactive input. Instead, it prompts for an API key interactively (see below).The cause can be traced back to the addition of
public_api = PublicApi()
on line 210 of wandb/cli.py. To my understanding, this causes the__init__()
method of thePublicApi
class (which triggers the interactive prompt if API key is unknown) to be called prior to the execution of any WandB CLI command. This behavior is undesirable, particularly because it renderswandb login <key>
useless except when a user is already logged in.What I Did
For now, working around this by downgrading to version 0.9.2.
The text was updated successfully, but these errors were encountered: