lakectl should handle redirects and other unexpected errors correctly.
My guess
lakectl uses the Swagger-generated client. A 3xx response is not possible according to this client. And it assumes some handling from the generated API client that does not actually occur.
lakectl need to handle such error gracefully
Other than that, we might want to investigate if the error itself is problematic, but lakectl should not segfault
I (mistakenly...) attempted to access an ancient playground account:
This demo account (
fancy-lion
) serves a redirect, probably because it's expired:lakectl should handle redirects and other unexpected errors correctly.
My guess
lakectl uses the Swagger-generated client. A 3xx response is not possible according to this client. And it assumes some handling from the generated API client that does not actually occur.