fix: handle internal error: tck failure#186
Conversation
Summary of ChangesHello @nahapetyan-serob, 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 failures in two TCK (Technology Compatibility Kit) tests by introducing an interceptor within the System Under Test (SUT) agent. The core issue stems from a divergence between the project's internal task continuation logic, which is more restrictive, and the broader expectations of the TCK tests. The added interceptor specifically modifies the SUT agent's responses for certain test messages, ensuring these particular TCK tests pass without altering the underlying task state management. Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request addresses a TCK failure by introducing an interceptor in the SUT agent. This interceptor specifically handles task continuation for non-terminal states, which was a gap in the previous implementation. The changes are well-contained within the test environment and the use of an interceptor is a clean way to inject this test-specific behavior. My feedback includes a suggestion to improve maintainability by replacing hardcoded strings with constants.
🤖 I have created a release *beep* *boop* --- ## [0.3.7](v0.3.6...v0.3.7) (2026-02-20) ### Features * implement tasks/list RPC ([#210](#210)) ([6e04698](6e04698)) * retry cancelations ([#222](#222)) ([3057474](3057474)) ### Bug Fixes * handle internal error: tck failure ([#186](#186)) ([b55fbfd](b55fbfd)) * **sse:** support data: prefix without space ([#188](#188)) ([6657a6d](6657a6d)), closes [#162](#162) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
The spec was unspecified, so the implementation restricts task continuation to TaskStateInputRequired. However, TCK tests expect continuation for any non-terminal state. Added an interceptor to the SUT agent so 2 of TCK tests would pass.