Disable forced PyTorch upgrades #1550
Closed
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.
Disables automatic PyTorch version upgrades by commenting out the ensureRecommendedNvidiaTorch() call in updatePackages().
Changed src/install/installationManager.ts:385 from:
await installation.virtualEnvironment.ensureRecommendedNvidiaTorch(callbacks);
To:
// Disabled forced PyTorch upgrades - users should control when large package downloads occur
// await installation.virtualEnvironment.ensureRecommendedNvidiaTorch(callbacks);
This prevents automatic 1.5GB PyTorch package downloads on app startup. NVIDIA users will keep their current PyTorch versions until they manually upgrade or a future PR adds opt-in upgrade prompts with user consent dialogs.
Tested: ESLint, TypeScript compilation, and pre-commit hooks all pass.
Related: PR #1513 (introduced the forced upgrade), PR #1525 (will add guided UX)
┆Issue is synchronized with this Notion page by Unito