Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Feb 7, 2026

Previously, we stored the shadow crate in target/hermes_shadow_<hash>.
Now we store it in target/hermes/<hash>/shadow. This allows us to
store other build artifacts in target/hermes/<hash> but outside of
/shadow to avoid polluting the shadow copy.


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/G7f8abd90b628d02a6fdc01985535eef50509312e && git checkout -b pr-G7f8abd90b628d02a6fdc01985535eef50509312e FETCH_HEAD

Checkout

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

Cherry Pick

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

Pull

git pull origin refs/heads/G7f8abd90b628d02a6fdc01985535eef50509312e

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 refactors the directory structure for Hermes build artifacts, specifically isolating the "shadow crate" within a dedicated subdirectory. Previously, the shadow crate was stored directly under target/hermes_shadow_<hash>. Now, it resides in target/hermes/<hash>/shadow, which provides a more organized approach. This change prevents potential conflicts and pollution of the shadow copy by allowing other build artifacts to be stored alongside it in target/hermes/<hash> without intermingling.

Highlights

  • Shadow Crate Isolation: The storage location for the 'shadow crate' has been moved from target/hermes_shadow_<hash> to a more isolated target/hermes/<hash>/shadow.
  • Improved Artifact Management: This new directory structure allows other build artifacts to be stored within target/hermes/<hash> without interfering with or polluting the shadow copy.
  • Code Refactoring: The Roots struct in tools/hermes/src/resolve.rs has been refactored to replace shadow_root with hermes_run_root and introduce a shadow_root() method for consistent path derivation.

🧠 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/resolve.rs
    • The Roots struct was modified: shadow_root: PathBuf was replaced with hermes_run_root: PathBuf, and a new public method shadow_root() was added to derive the full shadow path.
    • The function resolve_shadow_path was renamed to resolve_run_root and updated to construct paths under target/hermes/<hash>.
    • Path resolution logic was adjusted to incorporate the new hermes subdirectory.
  • tools/hermes/src/shadow.rs
    • All direct accesses to roots.shadow_root were updated to use the new roots.shadow_root() method for consistency with the refactored Roots struct.
  • tools/hermes/tests/integration.rs
    • Integration tests were updated to reflect the new shadow crate path. The HERMES_TEST_SHADOW_NAME environment variable and the expected actual_shadow path were adjusted accordingly.
Activity
  • The pull request was opened by joshlf with a clear description of the intent to isolate the shadow crate.
  • No further review comments or activity have been recorded.
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 refactors the directory structure for build artifacts generated by Hermes. The shadow crate is now stored in target/hermes/<hash>/shadow instead of target/hermes_shadow_<hash>, which better isolates it and allows for other artifacts to be stored alongside it. The implementation introduces a hermes_run_root in the Roots struct and a shadow_root() method for better encapsulation. The related functions and integration tests have been updated accordingly. The changes are well-structured, correct, and improve the organization of build artifacts.

@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 (b6dc5d4) to head (b3bfc03).

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

Previously, we stored the shadow crate in `target/hermes_shadow_<hash>`.
Now we store it in `target/hermes/<hash>/shadow`. This allows us to
store other build artifacts in `target/hermes/<hash>` but outside of
`/shadow` to avoid polluting the shadow copy.

gherrit-pr-id: G7f8abd90b628d02a6fdc01985535eef50509312e
@joshlf joshlf force-pushed the G833f306c404eb4d4f3d920a8b169a5570b3806a4 branch from 1b5bc18 to b6dc5d4 Compare February 10, 2026 23:18
@joshlf joshlf force-pushed the G7f8abd90b628d02a6fdc01985535eef50509312e branch from 7590938 to b3bfc03 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