Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Feb 7, 2026


Latest Update: v26 — Compare vs v25

📚 Full Patch History

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

Version v25 v24 v23 v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v26 v25 v24 v23 v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v25 v24 v23 v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v24 v23 v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v23 v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v22 v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v21 v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v20 v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v19 v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v18 v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v17 v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v16 v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v15 v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v14 v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v13 v12 v11 v10 v9 v8 v7 v6 v5 v4 v3 v2 v1 Base
v12 v11 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/G833f306c404eb4d4f3d920a8b169a5570b3806a4 && git checkout -b pr-G833f306c404eb4d4f3d920a8b169a5570b3806a4 FETCH_HEAD

Checkout

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

Cherry Pick

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

Pull

git pull origin refs/heads/G833f306c404eb4d4f3d920a8b169a5570b3806a4

Stacked PRs enabled by GHerrit.

@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 significantly enhances the diagnostic capabilities of the hermes tool by integrating detailed trace and debug logging. These additions are strategically placed within critical functions responsible for parsing, dependency resolution, and shadow crate construction, providing developers with a clearer view of the tool's internal operations and facilitating more efficient troubleshooting.

Highlights

  • Enhanced Logging: Extensive trace and debug level logging has been introduced across core hermes functionalities to provide better insights into execution flow.
  • Debug Trait Implementation: The Debug trait derivation was added to the Roots struct, enabling easier debugging and logging of Roots instances.

🧠 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 log::trace! to read_file_and_scan_compilation_unit to log the path being processed.
  • tools/hermes/src/resolve.rs
    • Applied #[derive(Debug)] to the Roots struct for debug printing.
    • Added log::trace! to resolve_roots to log its arguments.
    • Added log::trace! and log::debug! to resolve_shadow_path to log its entry and workspace root.
    • Added log::trace! to resolve_packages to log workspace and all arguments.
    • Added log::trace! to resolve_targets to log the package name.
    • Added log::trace! to check_for_external_deps to log its entry.
  • tools/hermes/src/shadow.rs
    • Added log::trace! to build_shadow_crate to log the Roots argument.
    • Added log::trace! to process_file_recursive to log the source path.
    • Added log::trace! to resolve_module_path to log base directory, module name, and path attribute.
    • Added log::trace! to create_symlink_skeleton to log various path arguments and skip paths count.
Activity
  • No specific activity has been recorded for this pull request yet.
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.

@codecov-commenter
Copy link

codecov-commenter commented Feb 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.87%. Comparing base (9b57bca) to head (b6dc5d4).

Additional details and impacted files
@@                            Coverage Diff                             @@
##           Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2    #3012   +/-   ##
==========================================================================
  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.

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 adds trace and debug logging across several files to improve the tool's observability. The changes are straightforward and well-implemented. I've suggested a minor formatting improvement for a long log line to enhance readability, but overall, the changes are good.

target_dir: &Path,
skip_paths: &HashSet<PathBuf>,
) -> Result<()> {
log::trace!("create_symlink_skeleton(source_root: {:?}, dest_root: {:?}, target_dir: {:?}, skip_paths_count: {})", source_root, dest_root, target_dir, skip_paths.len());
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

This line is quite long and exceeds typical line length limits (e.g., 100-120 characters), which can harm readability and maintainability. Consider formatting this log::trace! macro call across multiple lines to improve clarity.

    log::trace!(
        "create_symlink_skeleton(source_root: {:?}, dest_root: {:?}, target_dir: {:?}, skip_paths_count: {})",
        source_root,
        dest_root,
        target_dir,
        skip_paths.len()
    );

gherrit-pr-id: G833f306c404eb4d4f3d920a8b169a5570b3806a4
@joshlf joshlf force-pushed the G833f306c404eb4d4f3d920a8b169a5570b3806a4 branch from 1b5bc18 to b6dc5d4 Compare February 10, 2026 23:18
@joshlf joshlf force-pushed the Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2 branch from 53c4584 to 9b57bca Compare February 10, 2026 23:18
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