[bug] debug node cannot work now
cardenluo opened this issue · 9 comments
Describe the bug
No input for the debug and math now
Reproduction
No response
Expected behavior
No response
Operating System
Windows (Default)
Comfy Mode
Comfy Portable (embed) (Default)
Console output
No response
Additional context
No response
Did this happen after an update of Comfy? I'll look into it a bit later today thanks for the report
I just tried myself on the last master of comfy and it works fine:
Can you check the web console and paste any errors here?
There are no error prompts on the launcher, but there are some warnings on the web console. Could this be the cause?
It seems like there are multiple instances of mtb (or its web module)
This can be because a few months back you had to manually move the web folder of extensions, now it's done automatically so I think you have mtb web extensions in ComfyUI/web/extensions <- if there is an mtb folder there just delete it
https://github.com/chflame163/ComfyUI_LayerStyle
thanks a lot ,And this plugin conflicts with it, this plugin will create files in web/extensions , delete it and then it's normal.
Thanks I will report it upstream they use the old method but I'mnot sure how it ended up interfering with mtb
Thanks I will report it upstream they use the old method but I'mnot sure how it ended up interfering with mtb
Thank you MTB. I used an old version of the browser extension component in my work, and I updated it and resolved the issue.
@melMass Any chance we can reopen this issue?
I'm having exactly the same problem experienced by @cardenluo, but I am not using LayerStyle custom node suite. So it must be something else.
This is the wonderful list of JS errors generated when I load ComfyUI with the latest commit and all custom node suites fetched to the latest version:
Notice that my setup is composed of a macOS browser on a machine connecting to a local server on a Windows machine.
That said, the page is pointing to the right IP address in trying to load those js, and I can manually display the source code in the browser by simply clicking on the link in the Dev Tools.
@alessandroperilli I think it might be caused by #170 that I just fixed.
If not don't hesitate to open a new issue as I don't think there is relevant information to refer to in this issue