matterircd 0.7 sends privmsg that cannot be parsed

[jtdaugherty]

Hi,

I'm using matterircd 0.7 and it sent a message to my chat client that the client could not parse:

irc: too few arguments received from IRC server for command "privmsg" (received: 3 arguments, expected: at least 4)
irc: failed to parse command "PRIVMSG" (please report to developers):
:dwest!ysthswine3f8bgqqse38c1pg7c@https://mattermost.galois.com PRIVMSG #questions-and-feedback

I've spoken with the chat client authors (weechat) and they're claiming that this is not an RFC-compliant message. (That issue is at weechat/weechat#751.)

CC @dwest-galois

[42wim]

I can't reproduce this in 0.8. How did this happen ? How does this look from mattermost side (which version) ? Can you try matterircd 0.8 (and run with -debug) and try to reproduce it?

Seems like it received a empty message from mattermost

[jtdaugherty]

I think @dwest-galois messaged me from MatterMost while I was logged into Weechat. We've ugpraded to 0.8 since this happened, so I'll keep an eye out for it happening again. If we were to run with debugging enabled, what would that enable that we should pass on to you (e.g. log files, etc.)?

[42wim]

-debug dumps a lot of info on stderr, the same PRIVMSG would also be visible in the debug output. I'd need a few lines before, this would show what was send from mattermost.

But I think I just found the issue, your friend probably pasted an image in a channel/private message without a text.

[jtdaugherty]

Ah! Fantastic! I'll keep an eye out either way, but thank you for looking into this.

[jtdaugherty]

(And I was wrong: we will upgrade to 0.8 tomorrow.)

[42wim]

It's fixed in master now, but I suppose it didn't crash the weechat client ? just a log/warning message ?

[jtdaugherty]

Yeah, I only got the text I posted in the original report; the client did not crash.

[dwest-galois]

Is this going to be released in v0.8.1 or v0.9? I'm just looking for an ETA so that I can plan updates accordingly.

[42wim]

Sorry, no ETA yet. I'll do a v0.8.1 if there's a crashing/critical bug, but this is not the case for this one.
It depends on how many other bugs pop up.