-
Notifications
You must be signed in to change notification settings - Fork 327
Update the frontend to support async nodes. #4382
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
Conversation
These locations differ from either local ids (like `5`) or execution ids (like `3:4:5`) in that all nodes which are 'linked' such that changes to one node will apply changes to other nodes will map to the same id. This is specifically relevant for multiple instances of the same subgraph. These IDs will actually get used in a followup commit
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.
Thassalottacode. Looks great so far, but it is a very large PR that could be split up into its distinct features.
Will need to come back to finish up, but have paused and just left the raw notes made as I flicked through.
p.s. you can just revert the |
|
|
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.
This is 90% just removing type assertions. Using 'as' does much more than e.g. specifying a function return type. The latter holds you to the contract - as
skips a lot of type checking.
All except one of these should be click-to-commit batchable, for your convenience.
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.
LGTM!
Also fixes a number of bugs with subgraphs
This should NOT be merged until the relevant PR to core is merged: comfyanonymous/ComfyUI#8830
┆Issue is synchronized with this Notion page by Unito