genai: custom http client produces an error about "gRPC dial options"

[eliben]

Description of the bug:

This is because the caching client is created with gRPC now (the REST one isn't working in the API)

Actual vs expected behavior:

No response

Any other information you'd like to share?

No response

[eliben]

Reran this test locally recently.

Now it fails with:

creating cache client: google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information

@jba

[jba]

What is the exact command?

When I run all the tests from the repo root with go test -v ./..., I see only two failures, in TestLive/tools/direct and TestLive/files. Neither mentions ADC.

It's possible you have to run gcloud auth application-default login.

[eliben]

What is the exact command?

When I run all the tests from the repo root with go test -v ./..., I see only two failures, in TestLive/tools/direct and TestLive/files. Neither mentions ADC.

It's possible you have to run gcloud auth application-default login.

Why would users need to do a gcloud login though, this is the google AI SDK, not vertex?

[eliben]

What is the exact command?

When I run all the tests from the repo root with go test -v ./..., I see only two failures, in TestLive/tools/direct and TestLive/files. Neither mentions ADC.

fwiw, #224 should fix some of the files failures (the API expectations changed)

[leventov]

custom HTTP client still doesn't work: https://discuss.ai.google.dev/t/gemini-flash-2-0-error-403-method-doesnt-allow-unregistered-callers/54123/5?u=roman_leventov

[jba]

@leventov, according to the thread you linked above, you have a solution. I agree that the solution could be nicer, but other than that, is there any action we should take?

[jba]

We recommend switching to the new client, google.golang.org/genai, and filing bugs on its issue tracker.