-
Notifications
You must be signed in to change notification settings - Fork 122
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
WAS_VAE_Input_Switch.vae_switch() got an unexpected keyword argument 'boolean_number' #364
Comments
A probably very bad workaround? #365 |
the latest update seems to have messed up the variable types in switches - I had workflows that used NUMBER as input, and now it seems it's not going to work anymore. |
That breaks sharing your workflow with others. It's such a minor fix, I hope it will be implemented soon. |
It's been almost a month since the last commit, and I don't love the idea of people using my janky hack code as a workaround, so hopefully this can get some attention soon! |
Error from VAE Input Switch:
`Error occurred when executing VAE Input Switch:
WAS_VAE_Input_Switch.vae_switch() got an unexpected keyword argument 'boolean_number'
File "E:\stable\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "E:\stable\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "E:\stable\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))`
The text was updated successfully, but these errors were encountered: