Open whd opened 10 years ago
@whd looks like it's caused by '/part' without channel parameter. It looks strange... Could you describe more or less how to reproduce this issue?
It isn't necessarily without the channel parameter, but rather, since the IRC response to parting is asynchronous, the IRC server just happened to not provide an IRC channel which was parted in response to the actual PART command.
IE: You can /part and eventually the IRC server acknowledges this, and responds with a message about you PARTing, in the normal case that response will include which server you parted from, but in this case it didn't...which is weird since you can't really just part from no channel as far as I'm aware.
which was parted in response to the actual PART command.
Yes, you're right. That's what i meant in my fuzzy way.
which is weird since you can't really just part from no channel as far as I'm aware.
Yeah, it violates RFC in my opinion. I can mock this but it would be good to test it against real scenario.
I'm curious if this happens when the bot can't join a channel after so many attempts, and then parts. But given it never successfully joined, it parts with no channel actually joined? I'm not really sure, just a thought.
With 0.7.2. This was probably due to an IRC channel key change, which coincided with the failure.