Conversation
|
Hi @jacob314, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
Summary of ChangesHello @jacob314, 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 addresses flakiness in Windows tests by refining the terminal rendering utility used in the test suite. The changes aim to standardize how terminal output is captured and asserted, particularly by removing platform-specific workarounds and adjusting terminal buffer dimensions to prevent rendering inconsistencies on Windows. 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 aims to fix flaky tests on Windows by adjusting the test rendering utility. The primary change in packages/cli/src/test-utils/render.tsx increases the headless terminal's row count, which is a pragmatic workaround for platform-specific rendering issues and allows for the removal of a Windows-specific code path. While this change is reasonable, the updated test snapshots reveal a new issue: duplicate test cases are being generated and added. This significantly impacts test suite maintainability and should be addressed by fixing the underlying test structure rather than committing redundant snapshots.
packages/cli/src/ui/components/__snapshots__/ConfigInitDisplay.test.tsx.snap
Show resolved
Hide resolved
|
Size Change: -2 B (0%) Total Size: 24.5 MB ℹ️ View Unchanged
|
Summary
Fixes #18499
Details
Revert hack ignoring xterm.js on windows replacing it with a less bad hack to use a larger than reasonable terminal height.