Conversation
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
thacio
added a commit
to thacio/auditaria
that referenced
this pull request
Aug 21, 2025
silviojr
pushed a commit
that referenced
this pull request
Aug 21, 2025
acoliver
referenced
this pull request
in vybestack/llxprt-code
Sep 11, 2025
involvex
pushed a commit
to involvex/gemini-cli
that referenced
this pull request
Sep 11, 2025
reconsumeralization
pushed a commit
to reconsumeralization/gemini-cli
that referenced
this pull request
Sep 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

TLDR
This pull request fixes a bug in the file search functionality that prevented it from finding files with special characters (like parentheses) in their paths. The search pattern is now unescaped before being used, ensuring that paths with special characters are resolved correctly.
Dive Deeper
The
RecursiveFileSearchimplementation was passing the user-provided search pattern directly to thefzfengine. This caused issues when a path contained special characters that are typically escaped in a shell environment (e.g.,src/file (special).txt). A user trying to find this file might provide an escaped pattern likesrc/file \\(special\\).txt.This change introduces a call to a new
unescapePathutility function, which normalizes the search pattern by removing shell escapes. This ensures that the search engine looks for the literal file path, allowing it to find files with special characters correctly.A new unit test has been added to verify this specific scenario, ensuring that a file with a path containing
(special)can be found using an escaped search pattern.Reviewer Test Plan
touch "my-file-(1).log"look at @my-file-\(my-file-(1).logas a suggestion.Testing Matrix