Closed melMass closed 5 months ago
@AustinMroz would there be any consequences for this behavior with the way our code is set up? If not, then I think we can merge this in
This looks super neat.
Only potential issue I see is it breaking the best effort support for nodes that output a list of tensors instead of a tensor. (#176)
Oh good point! I'm still not used to comfy's list concept.
Let me add an isisntance
clause it shouldn't "cost" a lot.
I pushed the fix, let me know if there is any issue left.
Attached is a workflow to test it:
instructions
output
The images input should always be a tensor. I consider it a bug of whatever other node is sending a list, but would like to avoid breaking peoples workflows where possible. Looks good to merge.
Thanks!
Hey Kosink,
This PR simply adds a safe bail for empty
IMAGE
input. I use this trick withBatch From History
you can test a basic sample of the issue here