At this stage, our Discord server would be the best place! I realize I did not mention this on the blogpost, that's now been amended! If you need access to the private channel mentioned in the updated post, ping me once you join and I can provide you access.
to achieve parallel execution and out-of-process node execution (which i guess the direction forward is going to be execution of multiple branches after a topo sort) you dont really need make everything async.
> There is no issue with calling non-async code from async call, so you can continue using whatever libraries you like
this is not true at all! you introduce a risk of blocking event loop which will be crucial during the execution. you might go with converting everything to threads from coro's but then what is the purpose of having everything as coro's then?
the dependency resolution is still a mystery to me. assuming a custom node declares a dependency on `some-package==2.0.0` and comfy has `some-package==3.0.0` how does the solution described in this specification help with that?
this is all very important. We ourselves are already working on distributing the workload on multiple GPUs in our pipeline with an AWS Deadline integration. more stability will also help a lot. Thanks!
This sounds great! How can a custom node developer give feedback so that it is taken into account before v3 is finalized?
At this stage, our Discord server would be the best place! I realize I did not mention this on the blogpost, that's now been amended! If you need access to the private channel mentioned in the updated post, ping me once you join and I can provide you access.
to achieve parallel execution and out-of-process node execution (which i guess the direction forward is going to be execution of multiple branches after a topo sort) you dont really need make everything async.
> There is no issue with calling non-async code from async call, so you can continue using whatever libraries you like
this is not true at all! you introduce a risk of blocking event loop which will be crucial during the execution. you might go with converting everything to threads from coro's but then what is the purpose of having everything as coro's then?
the dependency resolution is still a mystery to me. assuming a custom node declares a dependency on `some-package==2.0.0` and comfy has `some-package==3.0.0` how does the solution described in this specification help with that?
this is all very important. We ourselves are already working on distributing the workload on multiple GPUs in our pipeline with an AWS Deadline integration. more stability will also help a lot. Thanks!
will need more example or docs to get to this new version guidelines.