[Bug] Nil pointer deref in res.Usage in ListVectors call

[Southclaws]

Is this a new bug?

• I believe this is a new bug
• I have searched the existing Github issues and Community Forum, and I could not find an existing post for this bug

Describe the bug

Upon calling ListVectors it fails with a nil pointer panic. While debugging, I can see the field the code is trying to read is nil.

Error information

After the grpc call to res, err := (*idx.dataClient).List(idx.akCtx(ctx), req) err is nil but res looks malformed, the res.Usage pointer is nil but the current code tries to read ReadUnits without first checking Usage for nil.

Steps to reproduce the issue locally

Call ListVectors with any args, it seems.

Environment

• Go SDK version: v1.1.1

[jacob-brown]

same issue here with ListVectors.

I find that running with go run . works but building causes the null pointer error.

(edit) looks like older versions of the SDK also have the issue v1.0.0 to v1.1.1 (latest)

(edit) turns out mine was a bit of a blunder, I was trying to get the vectors for a namespace that doesn't exist!
Changing to the correct namespace resolved my issue however, it would be better to have ListVectorsResponse returned with empty slice for VectorIds.

hope the feedback helps the pinecone team
@Southclaws - double check you are calling with the intended config as the error msg didn't make this clear