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

🐛 Bug: When in Colab environment, get_secret() does not prompt for user input #24

Closed
aaronsteers opened this issue Feb 12, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@aaronsteers
Copy link
Contributor

aaronsteers commented Feb 12, 2024

This is due to Colab raising an exception rather than returning None. To fail-over to prompt behavior, we should catch the exception and try the next strategy in the list.

Resolved by:

@aaronsteers aaronsteers added the bug Something isn't working label Feb 12, 2024
@aaronsteers aaronsteers changed the title Bug: When in Colab environment, an unset secret does not allow prompt input 🐛 Bug: When in Colab environment, an unset secret does not allow prompt input Feb 12, 2024
@aaronsteers aaronsteers changed the title 🐛 Bug: When in Colab environment, an unset secret does not allow prompt input 🐛 Bug: When in Colab environment, an unset secret does not prompt for user imput Feb 12, 2024
@aaronsteers aaronsteers changed the title 🐛 Bug: When in Colab environment, an unset secret does not prompt for user imput 🐛 Bug: When in Colab environment, get_secret() does not prompt for user imput Feb 12, 2024
@aaronsteers aaronsteers changed the title 🐛 Bug: When in Colab environment, get_secret() does not prompt for user imput 🐛 Bug: When in Colab environment, get_secret() does not prompt for user input Feb 12, 2024
@aaronsteers aaronsteers self-assigned this Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant