Hello all. I'm attempting to use flytectl 0.5.25 on Centos7. I am trying to create a project. I keep getting the attached SIGSEGV, similar to (but not exactly) the issue here: https://github.com/flyteorg/flyte/issues/1320. What am I doing wrong here?

@ambitious-australia-27749, a few questions to help in the investigation: 1. can you share the exact stack trace you're seeing? 2. Do you see this with any workflow you attempt to register? 3. Can you say more about your flyte deployment ? (In other words, are you seeing this in a sandbox, eks, gcp) ?

Hi @high-accountant-32689! Thank you for the questions. Here are some answers to the best of my ability. I'm new to Flyte and am picking up this task from someone else, so my apologies in advance if I'm missing something obvious. 1. The attached cmdline.txt is the output I get when I run the command "flytectl create project --name test --id test --description "test" --labels app=test". Is there something more I need to attach?

@ambitious-australia-27749, no need to apologize, this should have worked. A couple more questions: 1. Did you mean to attach a file? 2. When you say you're running a single local k8s cluster, is it using minikube (or some other single node k8s) or you set up the machinery (i.e. kubelet, certificates, etc) yourself?

@high-accountant-32689 I have attached it here let me know if it's visible!

Hi @ambitious-australia-27749, this might point to your config endpoint being empty. Did you run

flytectl config init --host=<http://flyte.myexample.com|flyte.myexample.com>

Seems you don’t have any config setup and exposes a bug . Do you mind opening an issue for it. If you have your config set with endpoint details then it wont have thrown this trace. This is due to recent change. cc : @glamorous-carpet-83516