Suraj Sharma
Suraj Sharma
@seanzhou1023 Please have a look into it.
@danicat Your workaround using `rag.retrieval_query()` directly is correct - the issue is that `VertexAiRagRetrieval` adds RAG config to every Gemini 2+ request (even "hello"), likely triggering validation calls that exhaust...
@danicat The function approach gives you explicit control over the search query, which makes debugging and monitoring much easier. With the current tool implementation, the query generation happens internally within...
@adityapandey216 Good catch on the retry mechanism.That's definitely useful as an interim mitigation to handle transient 429s, though it won't solve the underlying issue of unnecessary RAG calls happening on...
@xuanyang15 Please have a look into it.
@simone-viozzi This is a known issue in v1.19.0 where transcription fields weren't properly stored/retrieved from session events during agent transfers. The fix was committed on Nov 19 (commit 3ad30a58) which...
@sayanb After analyzing the code and tests, the current behavior is actually by design - `output_key` only saves responses from the owning agent, not delegated sub-agents. This is validated by...
@rrbemfica The issue is that ADK's function parser doesn't support Python 3.10+ pipe operator union syntax (|) in function signatures. As a workaround, replace `List[str] | None` with `Union[List[str], None]`...
@busbaby the documentation shows the modern pipe operator syntax because that's the recommended Python 3.10+ style, but the parser hasn't been updated to support it yet. This is definitely a...