hubot replies result in "Invalid RootId parameter" messages and no output

[rickknowles-cognitant]

hubot replies result in "Invalid RootId parameter" messages and no output

[rickknowles-cognitant]

If anyone else needs a quick workaround, just change your package.json to this temporarily (note the lack of carets on package versions):

{
  "dependencies": {
    "hubot-matteruser": "5.3.1",
    "mattermost-client": "6.2.0"
  }
}

Confirmed it worked for me

[rickknowles-cognitant]

I came across this post from a similarly described error in another project in case it helps:

42wim/matterbridge#803

The fix was:

42wim/matterbridge@0b03076

[loafoe]

hi @rickknowles-cognitant I don't have direct access to a mattermost server at this time to replicate the issue but will try to understand the issue in the next couple of days

[rickknowles-cognitant]

OK sure thanks. In the meantime I've narrowed it down to being something that was introduced between v5.3.1 and v5.4.0.

I forced the use of mattermost-client-6.2.0 with hubot-matteruser 5.3.1 and the problem didnt happen, so I'm fairly confident diffing those two versions of hubot-matteruser is a good place to start

HTH

[rickknowles-cognitant]

Based on the error message, I'd be willing to bet it's in here somewhere:

[loafoe]

@jgarec any thoughts on this?

[rickknowles-cognitant]

Sorry forgot to mention the mattermost versions I tested this with were v5.22 and v5.26, same results in both cases

[jgarec]

Hi

Could you give me more details ?
Is it a direct message or on a channel ?
Could you paste a minimalist hubot script to reproduce ?

Thx

[jgarec]

Sorry, there was a little error in my previous PR

[loafoe]

thanks for fixing @jgarec

@rickknowles-cognitant version 5.4.1 should contain the fix for this

[rickknowles-cognitant]

Confirmed - deployed. this worked a treat. Thank you