feat: apply markdown rendering to HITL email, sanitize email subject and body#32305
Conversation
Summary of ChangesHello @Blackoutta, 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 security posture of outbound emails by integrating robust HTML and subject sanitization. It addresses potential vulnerabilities arising from untrusted HTML content in emails by introducing configurable sanitization profiles, ensuring that only safe and intended elements are delivered to recipients. This change improves the integrity and safety of email communications within the system. 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 introduces robust HTML sanitization for emails using the nh3 library and hardens email subject handling, providing strong security against XSS and CRLF injection attacks. While no critical security vulnerabilities were identified, there is a critical bug in the background task where the email subject is not rendered, causing template variables to be ignored. Further improvements include making the sanitize_email_subject function more concise and clarifying misleading test names in the new unit tests. The critical bug in the mail task must be addressed before merging.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Manipulate sys.path inside test making test fragile and hard to reason. Instead of manully append / prepend sys.path, we set the `pythonpath` option for pytest, so the PYTHONPATH and import path are automatically determined by the location of `pytest.ini`. We also set the `--import-mode` to `importlib` to prevent pytest from prepending paths to sys.path. ref: - [pytest import mechanisms and sys.path/PYTHONPATH](https://docs.pytest.org/en/stable/explanation/pythonpath.html#pythonpath) - [Initialization: determining rootdir and configfile](https://docs.pytest.org/en/stable/reference/customize.html#finding-the-rootdir)
remove unused import in test code
Pyrefly DiffNo changes detected. |
|
Hi @Blackoutta, I have revised the PR and introduced markdown rendering as part of the PR. I've also added SMTP header injection protection to this PR. |
Pyrefly DiffNo changes detected. |
awesome! |
Fixes #32304
Fixes #33513
Summary
nh3~=0.3.2.Checklist
make lintandmake type-check(backend) andcd web && npx lint-staged(frontend) to appease the lint gods