fix(server): resolve provider update command spawns#3171
Draft
Andrew-Forster wants to merge 1 commit into
Draft
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Summary
Provider update commands now go through the shared
resolveSpawnCommandpath beforeChildProcess.make, matching the provider/runtime process paths that already handle Windows.cmdand.batshims.Why
On Windows, package-manager commands such as
npmoften resolve to shim files likenpm.cmd. The provider update runner was still spawning the raw command name, so one-click Codex updates could fail withNotFound: ChildProcess.spawn (npm install -g @openai/codex@latest)even though the same command worked from a terminal. This keeps the command allowlist/update flow intact while reusing the centralized shim resolution and escaping added for other process spawns. Fixes #2765.Validation
pnpm --dir apps/server exec vp test run src/provider/providerMaintenanceRunner.test.tspnpm exec vp run --filter t3 typecheckpnpm exec vp checkpasses with existing warnings outside this changeNote
Resolve Windows command shims before spawning provider update commands
ProviderMaintenanceRunner.runCommandnow callsresolveSpawnCommandbefore spawning, which may transform the command/args and setshell: truewhen the resolved executable is a.cmdshim on Windows.linuxHostPlatformLayerto existing cases and add a new case asserting that Windows shim resolution produces the correct escaped command, args, andshell: true.CommandOptionsto the handler, enabling assertions on spawn options..cmdshim, changing the process spawning behavior for those environments.Macroscope summarized 60b77c5.