boundary

One of my tests stopped working... did Gemini 2.0 Flash maybe change recently?

So my Gemini Flash 2.0 unit tests started timing out since Gemini 3.0 came out and I just had to switch to Gemini 2.5 Flash Lite - same price last time I checked. It works! Before it didn't work as well. It is MUCH faster now.

Does it still happen? Can you paste de test and function to reproduce it?

Flash Lite helps, and it says it times out. I set the timeout to ten minutes via the Python option but it still happens.

does it time out after the 10 minutes? what kind of error do you see in the logs?

that will help understand if it's a baml timeout error or a provider http 500 timeout error kinda thing

It timed out quickly, not sure why. I tried splitting it into smaller data and it helps.

<@201399017161097216> are timeouts new in 0.215.0?

What am I doing wrong?
```
client<llm> Gemini20Flash {
    provider google-ai
    retry_policy Exponential
    options {
        model "gemini-2.0-flash"
        api_key env.GEMINI_API_KEY
        http
        {
            time_to_first_token_timeout_ms 60000
            idle_timeout_ms 60000
        }
        generationConfig {
            temperature 0.0
        }
    }
}
```

does it really break if you put the curly below? wow that is bad

I think that was it, but one of my tests still fails, debugging...

Some of my tests show incomplete output endings but they show complete raw JSON strings.

`Cannot hoist classes "Customer", "Supplier", "IntellectualProperty", "Acquisition", "MaterialContract" because they do not exist (in prompt:25)` - do they have to exist in the same file?

no, can you try reloading the window? (command shift p -> reload window)