Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Feb 12, 2026


This PR is on branch hermes.

Latest Update: v11 — Compare vs v10

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v8 v7 v6 v5 v4 v3 v2 v1 Base
v7 v6 v5 v4 v3 v2 v1 Base
v6 v5 v4 v3 v2 v1 Base
v5 v4 v3 v2 v1 Base
v4 v3 v2 v1 Base
v3 v2 v1 Base
v2 v1 Base
v1 Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/Gegf4fywvkwtqzwzektqc5lett4skoxvx && git checkout -b pr-Gegf4fywvkwtqzwzektqc5lett4skoxvx FETCH_HEAD

Checkout

git fetch origin refs/heads/Gegf4fywvkwtqzwzektqc5lett4skoxvx && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/Gegf4fywvkwtqzwzektqc5lett4skoxvx && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/Gegf4fywvkwtqzwzektqc5lett4skoxvx

Stacked PRs enabled by GHerrit.

gherrit-pr-id: Gegf4fywvkwtqzwzektqc5lett4skoxvx
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @joshlf, 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 enhances Hermes's parsing capabilities by introducing a warning for #[cfg_attr(..., path = "...")] attributes. This change addresses a current limitation where Hermes does not process conditional paths, ensuring that users are informed when their annotations might be overlooked due to this behavior. The update improves the robustness and user feedback of the tool without altering its core parsing logic for non-conditional paths.

Highlights

  • Conditional Path Warning: Implemented a warning mechanism in Hermes to alert users when #[cfg_attr(..., path = "...")] directives are used, as Hermes does not currently evaluate these conditional paths, potentially leading to ignored annotations.
  • Attribute Parsing: Added a new helper function, extract_cfg_attr_path, responsible for parsing cfg_attr attributes and extracting the specified path value if present.
  • Integration Tests: Introduced new integration tests to ensure the warning for cfg_attr paths is correctly triggered and reported, including setting specific log levels for testing.

🧠 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
  • tools/hermes/src/parse.rs
    • Added a warning for modules using #[cfg_attr(..., path = "...")] directives.
    • Implemented extract_cfg_attr_path function to identify and extract path values from cfg_attr attributes.
  • tools/hermes/tests/fixtures/warn_cfg_attr_path/expected_status.txt
    • Added expected status file for the new test case.
  • tools/hermes/tests/fixtures/warn_cfg_attr_path/expected_stderr.txt
    • Added expected stderr output for the new test case, containing the warning message.
  • tools/hermes/tests/fixtures/warn_cfg_attr_path/rust_log.txt
    • Added configuration file to set RUST_LOG to 'warn' for the test case.
  • tools/hermes/tests/fixtures/warn_cfg_attr_path/source/Cargo.toml
    • Added Cargo.toml for the new test fixture crate.
  • tools/hermes/tests/fixtures/warn_cfg_attr_path/source/src/lib.rs
    • Added source file with a #[cfg_attr(..., path = "...")] attribute to trigger the warning.
  • tools/hermes/tests/integration.rs
    • Modified the test runner to read RUST_LOG environment variable from rust_log.txt in test fixtures.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 warning for #[cfg_attr(..., path = "...")] attributes on modules, as Hermes does not support conditional path evaluation. This is a useful addition to inform users about potential issues. The implementation involves a new function to extract the path from the attribute and modifications to the AST visitor. The integration test suite is also enhanced to allow setting log levels, which is used to verify the new warning.

The changes are well-implemented. I have one suggestion to improve the new extract_cfg_attr_path function by simplifying some nested logic and adding error handling for a currently ignored Result, which will improve robustness and debuggability.

Comment on lines +467 to +478
let _ = attr.parse_nested_meta(|meta| {
if meta.path.is_ident("path") {
if let Ok(value) = meta.value() {
if let Ok(lit) = value.parse::<Lit>() {
if let Lit::Str(lit_str) = lit {
found_path = Some(lit_str.value());
}
}
}
}
Ok(())
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The result of attr.parse_nested_meta is ignored. It's better to handle the Result, for example by logging errors, to aid in debugging. Additionally, the nested if statements for parsing the literal can be simplified by combining them.

Suggested change
let _ = attr.parse_nested_meta(|meta| {
if meta.path.is_ident("path") {
if let Ok(value) = meta.value() {
if let Ok(lit) = value.parse::<Lit>() {
if let Lit::Str(lit_str) = lit {
found_path = Some(lit_str.value());
}
}
}
}
Ok(())
});
if let Err(e) = attr.parse_nested_meta(|meta| {
if meta.path.is_ident("path") {
if let Ok(value) = meta.value() {
if let Ok(Lit::Str(lit_str)) = value.parse() {
found_path = Some(lit_str.value());
}
}
}
Ok(())
}) {
trace!("Failed to parse nested meta in `cfg_attr`: {}", e);
}

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.87%. Comparing base (6b700a8) to head (4aaf99d).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           Gulbf5jp7zpz4nn77nspxpsiy3tadde54    #3045   +/-   ##
==================================================================
  Coverage                              91.87%   91.87%           
==================================================================
  Files                                     20       20           
  Lines                                   6057     6057           
==================================================================
  Hits                                    5565     5565           
  Misses                                   492      492           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants