Skip to content

Conversation

@ChrisQlasty
Copy link

Problem:
ADK seems to not pass output/input transcription finished flag from the Gemini.

Solution:
Relaxation of checking conditions of valid llm_response for input/output transcription.

Testing Plan

Unit test test_receive_transcript_finished checks if input/output transcription message with no text but finished flag is received.

Unit Tests:

  • I have added or updated unit tests for my change.
  • All unit tests pass locally.
image

Manual End-to-End (E2E) Tests:

Configure Gemini Agent to produce input & output transcriptions. Observe incoming transcript messages - to see if the finished flag appears at the end agents & users statement.

Checklist

  • I have read the CONTRIBUTING.md document.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have manually tested my changes end-to-end.
  • Any dependent changes have been merged and published in downstream modules.

Additional context

The mentioned finished flag can be obtained in native Gemini APIs like via Websocket but not via ADK.

@gemini-code-assist
Copy link

Summary of Changes

Hello @ChrisQlasty, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue where the ADK (Agent Development Kit) was failing to properly propagate the finished flag for input and output transcriptions originating from the Gemini API, particularly when these transcriptions lacked accompanying text. The core change involves relaxing the conditions for yielding LlmResponse objects, allowing them to be generated solely based on the presence of the transcription object, even if its text field is empty. This ensures that the system accurately captures and communicates the completion status of transcription segments. The functionality is validated by a newly introduced unit test.

Highlights

  • Relaxed Transcription Validation: The system now correctly processes input and output transcriptions from the Gemini API even when they contain only a 'finished' flag and no text, ensuring that completion signals are not missed.
  • New Unit Test Coverage: A dedicated unit test, test_receive_transcript_finished, has been added to verify the correct handling of the 'finished' flag for both input and output transcriptions, confirming the fix's effectiveness.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@adk-bot adk-bot added the live [Component] This issue is related to live, voice and video chat label Oct 28, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly addresses the issue of the finished flag not being passed for input/output transcriptions by relaxing the validation conditions in GeminiLlmConnection.receive. The change is simple and effective. The accompanying unit test, test_receive_transcript_finished, properly verifies this new behavior for both input and output transcriptions. I've added a couple of suggestions to the new test code to improve its conciseness and maintainability by reducing code duplication. Overall, this is a good fix.

@ChrisQlasty
Copy link
Author

Hello, is there any chance to have this bug fixed?
Let me ask you @hangfei as I see you are often involved.

Also I see that in general 'live' models seem to not have big interest from the ADK users and developers which is quite surprising.

@hangfei
Copy link
Collaborator

hangfei commented Nov 5, 2025

This is a good contribution. Could you resolve conflicts so we can merge?

Why do you think we have less interests from users?

@hangfei
Copy link
Collaborator

hangfei commented Nov 5, 2025

Please fix pyink, also close or resolve gemini code comments.

hangfei and others added 5 commits November 4, 2025 19:07
Added a new test for receiving usage metadata and server content.
Refactored Msg class to use a single mock instance and simplified transcription response checks.
@ChrisQlasty
Copy link
Author

Thanks for your response @hangfei!

I have resolved code comments and updated the PR according to merged main branch, so it looks clean again I believe.

The reason I assumed 'less interest' is that there are only few PR's in the adk-python, which have the 'live' label assigned. But maybe much more of the PR's and issues deal with it under other labels as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

live [Component] This issue is related to live, voice and video chat

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants