When won't there be an event? Is this something that came up in the test suite only?

@dwoz, I'm not sure exactly what triggered it, but we would see an error about self.event being None when running salt-call commands pretty reliably. This prevents the error, but I'm not sure how to even reproduce this in a test to be honest without having it be very contrived.

There won't be an event if the channel is already closed.

    def close(self):
        """
        Close the channel
        """
        self.transport.close()
        if self.event is not None:
            self.event.destroy()
            self.event = None

Is it possible this could get called after the channel is already closed?

@bdrx312, not sure if you're asking me or @dwoz. For my part, I'm not sure why the behavior is happening, only that it is happening. And sadly, I lack the deeper knowledge of salt's message bus handling to know exactly what's going on here.

I was asking @dwoz, trying to address his question of a way that there might not be an event. It seems appropriate to handle the case of there not being event here in case reconnect is called on when it was already closed.