Skip to content

Conversation

@joshlf
Copy link
Member

@joshlf joshlf commented Feb 7, 2026


Latest Update: v27 — Compare vs v26

📚 Full Patch History

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

Version 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
v27 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
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/Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2 && git checkout -b pr-Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2 FETCH_HEAD

Checkout

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

Cherry Pick

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

Pull

git pull origin refs/heads/Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2

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 enhances the hermes tool's UI testing capabilities and the precision of its diagnostic output. It includes significant improvements to how error messages are generated, ensuring more accurate line and column information, which is crucial for effective debugging. A new test case has also been introduced to validate the tool's error reporting for syntax issues, reinforcing its robustness.

Highlights

  • Improved Error Diagnostics: The logic for calculating line and column numbers, as well as extracting the full line text for error snippets, has been refined in emit_rustc_json to provide more accurate and helpful diagnostic output.
  • New UI Test for Syntax Errors: A new UI test (fail_syntax.rs) has been added to specifically verify the hermes tool's ability to correctly detect and report syntax errors, along with its expected stderr output.
  • Code Refinements in ui_test_shim.rs: Comments have been updated to clarify the ui_test shim's role in mimicking rustc behavior, the emit_rustc_json function has been made private, and the return value of read_file_and_scan_compilation_unit is now explicitly ignored when only errors are of interest.

🧠 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/ui_test_shim.rs
    • Updated comments for the run function to better describe its rustc-like behavior for ui_test.
    • Modified parse::read_file_and_scan_compilation_unit call to explicitly ignore its return value, focusing only on error handling.
    • Removed an outdated comment from the RustcSpan struct.
    • Changed the emit_rustc_json function's visibility from public to private, improving encapsulation.
    • Refined the calculation of line_start, column_start, and line_text within emit_rustc_json to enhance error snippet accuracy.
  • tools/hermes/tests/ui/fail_syntax.rs
    • Added a new UI test file to check for syntax error reporting.
  • tools/hermes/tests/ui/fail_syntax.stderr
    • Added the expected stderr output for the fail_syntax.rs UI test.
Activity
  • No specific activity (comments, reviews, etc.) 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.

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 a new UI test for syntax errors and includes several small improvements to the UI test shim. The changes improve code clarity and structure, such as making a function private and refactoring logic for better readability. I've found one medium-severity issue related to a potential panic when handling file paths, and I've provided a detailed suggestion for a more robust implementation.

}

pub fn emit_rustc_json(e: &HermesError, source: &str, file: &str) {
fn emit_rustc_json(e: &HermesError, source: &str, file: &str) {
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 function is called with file_path.to_str().unwrap() on line 47. This can cause a panic if the file path contains non-UTF-8 characters. To make the code more robust, consider changing this function's signature to accept a &Path instead of a &str.

This would allow you to use file.display().to_string() inside this function to safely handle the conversion, and change the call site to pass &file_path directly, removing the .unwrap().

Suggested changes:

  1. Update this function's signature:

    fn emit_rustc_json(e: &HermesError, source: &str, file: &std::path::Path) {
  2. Update the file_name assignment on line 110:

    file_name: file.display().to_string(),
  3. Update the call on line 47:

    emit_rustc_json(&e, source, &file_path);

@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 (db80a43) to head (9b57bca).

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

gherrit-pr-id: Gbeb9a3b076d434abb7e0a799fdb18c4ad9fb87a2
@joshlf joshlf force-pushed the G3220747e90b678c598c506be49219a8f75118988 branch from 03142cc to db80a43 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