When I use vertex in playground i get:

Unspecified error code: 2 Failed to create request builder: Error {
    context: "Failed to build request",
    source: Error {
        context: "Failed to load GCP creds: try running `gcloud auth application-default login`",
        source: JsCallbackRuntimeError {
            name: "Error",
            message: "Unable to detect a Project Id in the current environment. \nTo learn more about authentication and Google APIs, visit: \nhttps://cloud.google.com/docs/authentication/getting-started",
        },
    },
}

Request options: {}

But I can use

uv run baml-cli test

just fine.

Oh! @aaronv (BAML) or @lucablight4200 do yall know what the solution was?

Do you use a vertex api key or application credentials?

We use application defaulty credentials

i think there's an inherent bug in our playground reading the application credentials correctly. Let me see

thanks - i have baml-cli test running and am using that alongside my other unit tests. But hte playground is a nice feature so would be lovely to get it working 🙂

i run into the same error so i think i have enough of a repro to try to fix it, but no ETA yet. If you do want the playground definitely try the api key approach (if you can manage to get an exception). We just made that work in 0.208.5

The playground loads gcloud credentials using the IDE process in vscode edit: after refreshing my gcloud creds, our gcloud integration doesn't work for me, so I'll be looking at this tomorrow

OHHH, are you spawning a repo thats in a container from vscode? if so, i think whats happening is the

shell

command we use to get auth is running in the docker container. which in turn now needs to run

gcloud auth login

or something of that sort which then require the

~/.config/gcloud

file to then exist in that shell (which happens to be in the container)

https://github.com/BoundaryML/baml/pull/2525 is up to address this!

this has been released

Thanks for the quick turnaround! Correction: everything is working - looks like the Google auth client had cached bad creds. Thank you for your help! ~~ I am still getting an error though: Unspecified error code: 2 Failed to create request builder: Error { context: "Failed to build request", source: Error { context: "Failed to load GCP creds token: try running `gcloud auth application-default login`", source: JsCallbackTypeError( "loadGcpCreds rejected during promise await with Error: VSCode RPC request timed out after 5000ms: LOAD_GCP_CREDS", ), }, } Request options: {"generationConfig":{"temperature":0.0}} ~~

are you developing inside a container/ssh?

Nope - this is all in vscode on a Mac. Vscode opened as a regular Mac app. I can run the BAML tests from the vscode terminal or elsewhere just fine.

> Looks like restarting the playground plugin and vscode doesn’t seem to reload the credentials after an auth? huh. what did you have to reload to make it work?

Just time I think - I think the cached token would hit its expiry and then get refreshed

Blegh… I’ve definitely ran into similar with AWS before