-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[llvm-lit] Fix TypeError
string argument expected in lit's internal shell
#105925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Harini0924
wants to merge
1
commit into
llvm:main
Choose a base branch
from
Harini0924:bolt_typeError
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this change the call to
expand_glob_expressions
inexecuteBuiltinMkdir
andexecuteBuiltinRm()
can also be removed.It would probably also be good to add a test that checks something like the following
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I initially didn’t remove the call to
expand_glob_expressions
inexecuteBuiltinMkdir
andexecuteBuiltinRm
because removing it was causing an error. Here's the error I encountered:This error occurs because
args
wasn't being initialized correctly after I removed theexpand_glob_expressions(cmd.args, cmd_shenv.cwd)[1:]
line from these functions. The issue is that the functions still expect args to be expanded and processed, but when I rely solely on the expansion happening in_executeShCmd
, the arguments aren't passed in the correct form to these built-in functions.Specifically, in the context of commands like
mkdir
andrm
,args[0]
represents the command itself (e.g., mkdir or rm), and this should not be expanded. Expandingargs[0]
could cause the command to be mistakenly treated as a file or directory to expand, which would break the logic. Therefore, onlyargs[1:]
(the options or arguments) should undergo glob expansion. For example, in a command like mkdir -p folder*, we only want folder* to be expanded, not the command mkdir itself. Correct me if I am wrong, but that is what I was getting.In short, removing
expand_glob_expressions
from these functions without ensuring proper argument handling causes the built-in commands to fail when trying to accessargs
later in the flow, especially sinceargs[0]
should not be expanded.I'm also working on writing the other test. Let me know what you think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see expanding args[0] being a problem - I just tested with zsh and it just expands all globs:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And yes you will have to make additional changes to the builtinMkdir and builtinRM:
Instead of
args
(which came from the lineargs = expand_glob_expressions(cmd.args, cmd_shenv.cwd)[1:]
you just usecmd.args
.args
won't magically appear in this function if you remove the line that assigns to the variable.