mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1517] Follow-up: versioned settings migration for torch mirror defaults #442
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#442
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @benceruleanlu on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1517
Hotfix in place to migrate legacy cu129 torch mirror to cu130 for NVIDIA installs.\n\nFollow-up (long-term): move to versioned settings migrations in ComfySettings and track whether torch mirror was user-set vs default.\n\nProposed scope:\n- Add Comfy-Desktop.SettingsSchemaVersion + migration pipeline in ComfySettings.load()\n- Track default vs user-set torch mirror (e.g., TorchMirrorSource or TorchMirrorWasDefault)\n- Migrate legacy torch mirror only when it was default\n- Remove ad-hoc migration in ComfyInstallation/virtualEnvironment once schema migration exists\n\nNotes:\n- Hotfix can ship now; this issue replaces it with a safer long-term approach.\n
┆Issue is synchronized with this Notion page by Unito
@coderabbitai[bot] commented on GitHub (Jan 8, 2026):
🔗 Related PRs
Comfy-Org/desktop#1512 - Update NVIDIA PyTorch to 2.9.1 cu130 [merged]
Comfy-Org/desktop#1513 - Update NVIDIA torch version on updates [closed]
Enable issue planning
To enable issue planning, add the following to your
.coderabbit.yaml:You can then request a plan by commenting
@coderabbitai planon any issue.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
@dosubot[bot] commented on GitHub (Apr 9, 2026):
Hi, @benceruleanlu. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!