Open wild-endeavor opened 2 years ago
Note that while I saw this happen in real-time in the user's terminal, we are unable to repro this locally. Locally we get
$ flytectl get project
INFO[0000] [0] Couldn't find a config file []. Relying on env vars and pflags.
{"json":{},"level":"error","msg":"failed to initialize token source provider. Err: failed to fetch auth metadata. Error: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: missing address\"","ts":"2022-05-17T15:30:02-07:00"}
{"json":{},"level":"warning","msg":"Starting an unauthenticated client because: can't create authenticated channel without a TokenSourceProvider","ts":"2022-05-17T15:30:02-07:00"}
{"json":{},"level":"info","msg":"Initialized Admin client","ts":"2022-05-17T15:30:02-07:00"}
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: missing address"
{"json":{},"level":"error","msg":"rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: missing address\"","ts":"2022-05-17T15:30:02-07:00"}
I'm encountering the same issue. Running "flytectl config init" solved the first problem; but is there a workaround for the connection issue?
I solved the connection issue by creating a local sandbox. You can stick more helpful/descriptive error messages on the backlog ;)
Hello š, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! š
Hello š, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! š
we should make the UX better for flytectl
Hello š, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! š
Describe the bug
flytectl segfaults apparently when the config file is missing. User reported when creating and listing projects. Issue went away when we created a sandbox style config.yaml in the .flyte directory.
Expected behavior
A nice error message telling the user to run
config init
maybe?Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?