comfyanonymous
Comfy Local vs Cloud - priorities?
In the last month and updating daily ... ComfyUI Local has had 3 significant issues in the last month, basically forcing a Front-End rollback to solve the problem.
Have been a user & advocate of ComfyUI since it's inception.
Just yesterday, after launch, Comfy would just spin & the canvas would never populate ... after rolling back the Front-End, everything worked fine.
Question: With the introduction of "Cloud", has that taken precedent over Local?
The rash of errors Locally begs the question and makes me wonder about the focus on Local and if the future of Local will have any longevity ???
When Revenue becomes the priority, I've seen other open-source projects impacted by these business decisions and their resultant decline.......
The frontend is the same on local and cloud. If you want things to be as stable as on cloud don't install frontend extensions.
Just yesterday, after launch, Comfy would just spin & the canvas would never populate ... after rolling back the Front-End, everything worked fine.
Can you share the workflow? Would love to fix the issue
Just yesterday, after launch, Comfy would just spin & the canvas would never populate ... after rolling back the Front-End, everything worked fine.
Can you share the workflow? Would love to fix the issue
Thx! But actually on start would just spin & never populated. Rolled the FE back 2 ver (just to be safe) & everything worked perfectly fine. FYI - there have been a few FE issues over the last 4-6 weeks, and confirmed "like" issues with other AI colleagues
The frontend is the same on local and cloud. If you want things to be as stable as on cloud don't install frontend extensions.
No extensions installed. Have been using Comfy since it's inception.
But again, your answer doesn't Answer the real Question that I had posed. Priorities & Longevity for Local (free) vs Cloud (monetized) ???
Any other details that might help me reproduce the bug? Version number? The workflow saved that was trying to be restored? If it was an issue with restoring the last workflow you had opened, it might work normally now if you try again.