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

project list should not panic if the client is not authenticated #391

Closed
leftwo opened this issue Oct 9, 2023 · 1 comment
Closed

project list should not panic if the client is not authenticated #391

leftwo opened this issue Oct 9, 2023 · 1 comment

Comments

@leftwo
Copy link
Contributor

leftwo commented Oct 9, 2023

The CLI should not panic if it can't find an authenticated host:

Using this rev on my bench gimlet

EVT22200005 # ./oxide version
Oxide CLI 0.1.0-beta.5
Built from commit: 4959a447a543fb22511304a5f5f43df23b7ca9ee 
Oxide API: 0.0.1

I get this panic:

EVT22200005 # ./oxide project list
thread 'tokio-runtime-worker' panicked at 'no authenticated hosts', cli/src/context.rs:28:30
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(129), ...)', cli/src/main.rs:60:10
@ahl
Copy link
Collaborator

ahl commented Jul 17, 2024

Now we get:

$ oxide project list
no authenticated hosts; use oxide auth login to authenticate

@ahl ahl closed this as completed Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants