-
Notifications
You must be signed in to change notification settings - Fork 4
Two patches #55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Two patches #55
Conversation
Summary of ChangesHello @cgwalters, 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 consists of two main sets of changes: significant refactoring of the integration test suite to centralize command execution logic, and enhancements to the Highlights
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.
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 introduces a helpful refactoring for running commands in integration tests, which greatly improves code clarity and reduces boilerplate. The addition of JSON output for libvirt base-disks list
is also a valuable feature.
My main concern is the removal of timeout
wrappers from the integration tests. This could lead to CI pipelines hanging indefinitely if a command stalls. I've left comments with high
severity on this issue in the relevant test files.
I've also suggested a medium
severity improvement to use a clap::ValueEnum
for the new --format
option to improve type safety and user experience.
…upport Replace manual printf-style table formatting with comfy_table for consistent, well-formatted output across all list commands. Add --format=json support to base-disks list command to match the pattern used by other list commands, enabling machine-readable output for integration and scripting. Assisted-By: Claude Code Signed-off-by: Colin Walters <[email protected]>
cargo-nextest wraps each test in its own process, with a timeout and output capture. We don't need to do it in each test. This removes lots of boilerplate. Signed-off-by: Colin Walters <[email protected]>
No description provided.