Skip to content
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

INPUT_IS_LIST / OUTPUT_IS_LIST with ExecutionBlocker not working #2

Open
stephennilor opened this issue Aug 9, 2024 · 0 comments
Open

Comments

@stephennilor
Copy link

When i try to use the Crystools List of Any node, or my own nodes that implement INPUT_IS_LIST or OUTPUT_IS_LIST i get this error from the ExecutionBlocker when attempting to Block execution (i.e. not execute)

!!! Exception during processing !!! 'ExecutionBlocker' object is not iterable
Traceback (most recent call last):
  File "D:\comfy-guill\ComfyUI\execution.py", line 314, in execute
    output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
  File "D:\comfy-guill\ComfyUI\execution.py", line 219, in get_output_data
    output = merge_result_data(results, obj)
  File "D:\comfy-guill\ComfyUI\execution.py", line 179, in merge_result_data
    output.append([x for o in results for x in o[i]])
  File "D:\comfy-guill\ComfyUI\execution.py", line 179, in <listcomp>
    output.append([x for o in results for x in o[i]])
TypeError: 'ExecutionBlocker' object is not iterable

It seems like somehow one needs to be prepared to receive an ExecutionBlocker object instead of the usual inputs to a node, but I don't know what the best way of doing this is; could you advise how to support this node, because it's super helpful from an API call perspective.

To reproduce it, simply make a branching workflow with a Crystools List of Any after an Execution Blocker and dont execute that pathway (i think)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant