-
Notifications
You must be signed in to change notification settings - Fork 35
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
AttributeError: module 'comfy.sd' has no attribute 'ModelPatcher' #207
Comments
I know you are all very busy, but would it be possible to please get a response on this? |
I understand the importance of this feature. I have started working on temporarily fixing the node yesterday when I saw interest by the community in this issue. This problem is hard to solve consistently because it relies on very brittle hacks. As you already know, I opened an issue in comfyui for this matter: What I intend to do in the following days:
I don't know exactly yet how to get around 2). It doesn't seem like a straightforward thing to achieve given comfyui wasn't designed for this. |
Thank you so much for the response. That's wonderful news. I really appreciate all you are doing! |
If anyone can give a hand with the stability issue (point 2. above), we might get to it quicker. More stable solutions that don't rely on changing comfyui itself should be preferred over solutions that need to change comfyui. Although I haven't found a way that doesn't rely on direct changes in comfyui. Typically, to achieve what we want, comfyui would employ a strategy pattern where one implementation is an in-memory model, and the other is for remote models that can be located in a different process. The problem is, there are a lot of direct dependencies on the model class. Comfyui even adds their own custom methods to the class, some of which assume a state dict is directly available. Because of this, making this work in comyfui directly will raise the burden of maintenance in comfyui since it requires either a lot of changes or making two large model classes. When I get to it, I will experiment with multiple approaches. I cannot guarantee comfyanonymous will accept any potential solution I find. |
I think my own capability would be woefully inadequate for the task (I have some C++ experience and the rest of my programming dates back to QBasic/Pascal) but I will certainly do what I can to draw some attention to it! |
Is there nobody here willing or able to help @ljleb? This seems like something that would be thought of as essential for such an extension, I'm really surprised nobody has stepped up to the plate. I've been trying to learn python as fast as I can. |
Sorry about that. I don't use the extension much anymore, so I have little incentive to fix this. It would take a lot of time for me as well. If you figure it out, do make a PR. We still review them. |
No worries, I will likely try a crack of it out of curiosity and for learning purposes but mmmv given my own busy schedule and limited skillset. Given the rising popularity of sd-forge and other UI's, is it safe to assume development here isn't a priority? |
I mean, for now, the goal is to keep the repo in a working state at least for the main UIs (SDNext, Webui). If major breaking changes occur for the img2img and txt2img tabs, we should be able to address them pretty easily, and in a short period of time, in most cases. Adding new features to it, less of a priority right now for me at least, yes (assuming that's what you mean by "developpment isn't a priority"). |
I wouldn't mind if someone tried to make his own fork of the repo and fix all the basic issues that remain. I think that would amazing, the project isn't in MIT license for nothing. We'll definitely try our best to keep the repo in a working state until that happens, though. |
Sorry for the late reply - yes, that is what I meant. It's nice to see at least that dedication to not leaving anyone hanging. Cheers. |
Hello,
When trying to use the Webui Checkpoint node I get the following warning in sdwebui-comfyui window, "Error occurred when executing KSamplerAdvanced:"
Followed by the below terminal traceback
The text was updated successfully, but these errors were encountered: