WAS_VAE_Input_Switch.vae_switch() got an unexpected keyword argument 'boolean_number'

[adrian-forest]

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)))`

[adrian-forest]

A probably very bad workaround? #365

[wandrzej]

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. Wonder what's the plan for those switch nodes?

[Ionaut]

Check these in custom_nodes\was-node-suite-comfyui\WAS_Node_Suite.py

[nachocheeseburger]

Check these in custom_nodes\was-node-suite-comfyui\WAS_Node_Suite.py

sorry for being noob but what do we change here?

[Pos13]

Check these in custom_nodes\was-node-suite-comfyui\WAS_Node_Suite.py

That breaks sharing your workflow with others. It's such a minor fix, I hope it will be implemented soon.

[adrian-forest]

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!

[Pos13]

Speaking of jank hacks: as a temorary workaround, you can cast number to text and compare it to "1" to get a BOOLEAN.

[WAS-PlaiLabs]

https://github.com/WASasquatch/was-node-suite-comfyui/commit/7fb076611b4779e3943aa04925577c9e687653c7