isNull no longer working

[OnceWasPerfect]

the isNull node throws an error if the input actually is null. I believe it used to work, but haven't used in a bit. Throws the error if the input is bypassed or muted.

Edit: Sorry let me be good and include the relevant info
ComfyUI - Windows Portable v0.9.1
FrontEnd - 1.36.14
Basid Data Handling - 1.1.0

[StableLlama]

By disabling the input you have no input and so the node has nothing it can check for the input having a None (https://docs.python.org/3/library/constants.html#None)

This shows how to use it and for me it's working:

I guess you are looking for a node that checks whether the node has an input or not. This is currently not implemented in the Basic Data Handling nodes, but it could be a nice extension.

[OnceWasPerfect]

I suppose I was mistaken before but I could have sworn I used it like that before. In any case I ran your block of code for isnull through chatgpt and asked it to make it do what I wanted and it seems to have worked?

I'm no programmer so I have no idea if its good or robust but it is working. Here is what it came up with

class IsNull(ComfyNodeABC):
    """
    Checks if a value is None / unconnected.
    """
    @classmethod
    def INPUT_TYPES(cls):
        return {
            "required": {},
            "optional": {
                "value": (IO.ANY, {}),
            }
        }

    RETURN_TYPES = (IO.BOOLEAN,)
    RETURN_NAMES = ("is_null",)
    CATEGORY = "Basic/comparison"
    FUNCTION = "check_null"

    def check_null(self, value=None):
        return (value is None,)

[OnceWasPerfect]

Just an FYI, I think I figured out why I thought it was working. I use rgthree context nodes to pipe around data. Apparently they return an actual null if something is empty where as if you pass something into a subgraph that is empty outside that subgraph there is no "null". Here are two show any nodes, the top is from rgthree context node that has an empty image pipe, the bottom is from a subgraph input that has a bypassed image connected to it.

[StableLlama]

I've created #41 for you, that you get in version 1.2.0, where you get the "is connected" node.

It doesn't only detect whether it's connected or not (which is rather boring), but also returns False when the input is connected and bypassed (which is technically like being not connected). You can use that information e.g. with an if/else node to do different things and dynamically react on bypassed source nodes.

[OnceWasPerfect]

Awesome thank you, that will be most useful

[JonSingleton]

This "is connected" widget is the widget I never knew I needed. Just dropped by to say I saw this issue opened and checked back after you corrected it and saw you added that new widget. After having used it extensively in my workflows, I really just had to drop by and say thank you.