-
Notifications
You must be signed in to change notification settings - Fork 50
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
Migrate custom nodes #474
Migrate custom nodes #474
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected], npm/[email protected] |
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 can't us add anther custom_nodes
path in the yaml file that links folder and reinstall their dependencies in the new python environment? Currently this restoration of snapshots seems a bit award as it requires the python env to be ready first.
I don't think that is a very good method as:
I think having the same source for custom nodes between two different environments, with different comfy versions, packages, etc will cause more trouble than it is worth |
How about we directly copy the migration source's |
If we copy over the |
@pythongosssss FYI I synced with @ltdrdata and he mentioned he is planning to improve snapshot to also capture python package information. So I think we are good to go with the current approach. |
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.
Can you split the global toast change to a separate PR? I feel like having 2 levels of toast now can be confusing. For the custom node migration error reporting, we can fall back to use a electron system level message alert for now, and land the migration part first.
Adds custom node migration using manager snapshots
┆Issue is synchronized with this Notion page by Unito