CLI-3560: invalid memory address or nil pointer dereference when consuming a topic using a context

[natalia-ramos-bzy]

There is an error when using contexts when consuming from a topic

confluent kafka topic <topicName> --context dev
Error: runtime error: invalid memory address or nil pointer dereference

CLI details:

confluent - Confluent CLI

Version:     v3.40.0
Git Ref:     299e722ef
Build Date:  2023-11-02T23:32:56Z
Go Version:  go1.21.0 X:boringcrypto (windows/amd64)
Development: false

[brianstrauch]

Please update to v3.41.0 and let me know if that doesn't fix it.

[natalia-ramos-bzy]

I still have the same issue with v3.42.0:

confluent - Confluent CLI

Version:     v3.42.0
Git Ref:     41bf3c3ed
Build Date:  2023-11-16T20:20:16Z
Go Version:  go1.21.0 X:boringcrypto (windows/amd64)
Development: false

confluent kafka topic consume <topicName> --context dev
Error: runtime error: invalid memory address or nil pointer dereference

[brianstrauch]

Looks like our telemetry wasn't able to collect that runtime error and I'm unable to replicate it. Here are a few things you can try:

1. Give the command another run. If it results in a runtime error our telemetry systems should pick it up.
2. Build the CLI from source and run the command. You'll see the full stack trace which you can paste here.

[natalia-ramos-bzy]

Using v3.47.0 I get this new error:

confluent kafka topic <TopicName> --context dev
Error: required flag `--bootstrap` not set

[brianstrauch]

Did you mean to type "confluent kafka topic consume"?

[brianstrauch]

Also, as of v3.42.0 the --bootstrap flag is no longer required. Please check that you're using an up-to-date version. It sounds you may have multiple versions of the Confluent CLI installed, so make sure that the one you expect appears earlier in your $PATH.

[asiunov]

I get the same error when running the same command. No error when using the default context after confluent login --save. Does this command work with context?

confluent version v3.64.3