-
Notifications
You must be signed in to change notification settings - Fork 184
Fix: detect PowerShell 7+ (pwsh) in the UnsafeLocalCodeExecutor SHELL branch #568
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
Merged
kalenkevich
merged 9 commits into
google:main
from
AmaadMartin:fix/shell-executor-pwsh-detection
Aug 4, 2026
+60
−1
Merged
Changes from 5 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
adabe62
fix(code-executors): detect pwsh as a PowerShell shell command
08d386b
refactor(code-executors): simplify PowerShell command detection
271bf5e
refactor(code-executors): tighten PowerShell detection and its tests
f964527
test(code-executors): use vitest autospy for the spawn recorder
2f6ba68
test(code-executors): allow for PowerShell cold start in shell detection
449368a
fix(code-executors): keep shellCommandPath helper params optional
24a1be2
chore: park pwsh detection files at upstream state for merge
96d087c
Merge remote-tracking branch 'upstream/main' into fix/shell-executor-…
7aeb38e
fix(code-executors): detect pwsh as a PowerShell shell command
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.
why changed to be required?
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.
Good catch - reverted in 449368a, both
createTempScriptFileandgetExtensionForLanguagetakeshellCommandPath?: stringagain.The reasoning was that the only call site is
executeCode, which always passesthis.shellCommandPath, and the constructor defaults that to'powershell'/'bash'- so the optional made theundefinedcase unreachable. But that is a pre-existing cleanup and unrelated to this bug fix, so it did not belong in this diff. The new PowerShell check now guards the same way thecmdcheck on the next line already does:The diff is now only the pwsh detection fix. Happy to send the signature tightening separately if you want it.