Skip to content
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

Closed
brentschroeter opened this issue Jul 13, 2020 · 7 comments
Closed

CLI login command incorrectly triggers interactive prompt #1156

brentschroeter opened this issue Jul 13, 2020 · 7 comments
Labels
ty:bug type of the issue is a bug

Comments

@brentschroeter
Copy link

  • Weights and Biases version: 0.9.3
  • Python version: 3.6.9, 3.7.8
  • Operating System: Ubuntu 18.04, macOS 10.15.3

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 the PublicApi 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 renders wandb login <key> useless except when a user is already logged in.

What I Did

$ wandb login <my-api-key-here>
wandb: (1) Create a W&B account
wandb: (2) Use an existing W&B account
wandb: (3) Don't visualize my results
wandb: Enter your choice:

For now, working around this by downgrading to version 0.9.2.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.95. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the ty:bug type of the issue is a bug label Jul 13, 2020
@tyomhak
Copy link

tyomhak commented Jul 14, 2020

Thank you very much for reporting! We have filed a ticket for this.
Sorry for the inconvenience.

@ariG23498
Copy link
Contributor

Hey @brentschroeter
In the past few months we've majorly reworked the CLI and UI for Weights & Biases. We're closing inactivate threads for the time being. Please comment to reopen. 😄

@KhushalB
Copy link

@ariG23498 this issue is still there. Experienced it while trying to init as anonymous on a kaggle kernel

@ecthompson99
Copy link

@KhushalB did you figure out a workaround on the kaggle kernel? Running into this problem now.

@KhushalB
Copy link

@ecthompson99 setting anonymous='must' worked for me. Was not able to claim the runs from my wandb account after though.

@nateraw
Copy link

nateraw commented Jan 3, 2024

Same experience as @KhushalB - I can create anonymous runs but I can't claim them. Is claiming still supported somehow?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ty:bug type of the issue is a bug
Projects
None yet
Development

No branches or pull requests

6 participants