Conversation
waruqi
commented
Nov 19, 2025
- Before adding new features and new modules, please go to issues to submit the relevant feature description first.
- Write good commit messages and use the same coding conventions as the rest of the project.
- Please commit code to dev branch and we will merge into master branch in feature
- Ensure your edited codes with four spaces instead of TAB.
- 增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
- 编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
- 请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
- 为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。
Summary of ChangesHello @waruqi, 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 significantly enhances the user experience of 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.
Code Review
This pull request refactors the clang-tidy checker to improve its output handling by introducing a new _check_sourcefile function. This function is intended to run clang-tidy on a single file and provide more structured output. While this is a good improvement, I've found a critical bug in the new function's implementation that will cause a runtime error. My review includes a suggested fix for this issue. Once addressed, this change will enhance the checker's usability.
| local outdata, errdata = os.iorunv(clang_tidy.program, opt.tidy_argv, {curdir = opt.projectdir}) | ||
| return (outdata or "") .. (errdata or "") |
There was a problem hiding this comment.
The os.iorunv function returns four values: ok, outdata, errdata, errors. In the current implementation, local outdata, errdata = os.iorunv(...) incorrectly assigns the boolean ok status to outdata and the stdout content to errdata. This will cause a runtime error on the next line when attempting to concatenate a boolean value with a string.
Additionally, the command's exit status is not checked, so failed clang-tidy runs would not be handled correctly.
To fix this, you should capture all return values from os.iorunv, check the ok status, and handle failures by raising an error. On success, you can then correctly process outdata and errdata.
local ok, outdata, errdata, errors = os.iorunv(clang_tidy.program, opt.tidy_argv, {curdir = opt.projectdir})
if not ok then
raise({stdout = outdata, stderr = errdata, errors = errors})
end
return outdata, errdata