[diffusion] chore: forbid Chinese characters#18249
Conversation
|
/tag-and-rerun-ci |
Summary of ChangesHello @mickqian, 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 introduces a new pre-commit hook to enforce a consistent character set within the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. 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 adds a pre-commit hook to prevent Chinese characters in certain files. The implementation uses a complex one-liner Python script. While functional, this approach is difficult to read, debug, and maintain. I've suggested refactoring this into a separate, more readable Python script for better long-term maintainability.
| entry: >- | ||
| python3 -c 'import sys, re; p=re.compile(r"[\u4e00-\u9fff]"); ec=0; [ ([(print(f"{f}:{i+1}: {l.strip()}") or (ec:=1)) for i,l in enumerate(open(f, "r", encoding="utf-8", errors="ignore")) if p.search(l)]) for f in sys.argv[1:] ]; sys.exit(ec)' |
There was a problem hiding this comment.
This one-liner is quite complex and hard to read and maintain. It would be much better to move this logic into a separate Python script file. This improves readability, makes it easier to debug, and is more aligned with best practices like using with statements for file handling.
For example, you could create a script scripts/check_chinese_chars.py with the following content:
# scripts/check_chinese_chars.py
import sys
import re
CHINESE_CHAR_RE = re.compile(r"[\u4e00-\u9fff]")
exit_code = 0
for filename in sys.argv[1:]:
try:
with open(filename, "r", encoding="utf-8", errors="ignore") as f:
for i, line in enumerate(f, 1):
if CHINESE_CHAR_RE.search(line):
print(f"{filename}:{i}: {line.strip()}")
exit_code = 1
except Exception as e:
print(f"Error processing file {filename}: {e}", file=sys.stderr)
exit_code = 1
sys.exit(exit_code)Then, you can update the entry to simply call this script:
entry: python3 scripts/check_chinese_chars.pyThis change would make the hook's logic much more transparent and maintainable.
d3468b1 to
a396d15
Compare
Motivation
Modifications
Accuracy Tests
Benchmarking and Profiling
Checklist
Review Process
/tag-run-ci-label,/rerun-failed-ci,/tag-and-rerun-ci