-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
After updating the latest version, a BUG will appear in the prompt queue. #3686
Comments
see the browser log |
I have no idea how commit f374ea7 would cause this issue, unless it somehow introduced a namespace conflict that causes unexpected behavior downstream. |
I've looked into this since @davidchenhs originally filed a bug in rgthree-comfy. Looking into it, they're correct that f374ea7 introduces unintended behavior that causes auto-queue to fire while just dragging the canvas (whereas before that, it did not).
If this was not intended, then either that (Note, even before f374ea7 autoqueue would fire when moving a node and, arguable, that's not necessary). |
With all that said, I'm curious, @davidchenhs, what issue this really causes and if there's more to this than I see. If the prompt hasn't changed, no real work is being done even if its sent to the server. It's not much more than a simple ping-pong. Perhaps it was just the log messages that appear (rgthree-comfy, timing, etc) that appear over and over? |
Under complex workflow conditions, if I add a prompt queue, the queue will be repeated many times. Not only the log will be repeated, but the loading of the nodes inside will also be repeated. For example, if I use a node that plays sound, when After I add the prompt queue, it will keep making sounds |
Chrome |
I found that switching versions can improve the automatic execution of the drag interface, but if there is rgthree's image compare node, there will be a situation where the parameters are adjusted once and then the queue is loaded all the time. I finally changed back to the 0fecfd2 version and disabled rgthree's image compare node. The method perfectly solved the problem. @rgthree @shawnington @ltdrdata |
I spent two nights reinstalling the nodes and dependencies, and finally found out that it was a version update problem, which caused a bug in the queue. Under the condition that it is automatically executed when the status changes, dragging the mouse or other operations will also be executed.
The text was updated successfully, but these errors were encountered: