We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After calling the \zoom command, a new user was referred to by id instead of username.
\zoom
We suspect this bug is related to an issue filed in the flowdock adapter repo:
res.reply doesn't use user's display name if they joined flow after Hubot started
However that issue suggests that restarting Hubot will fix the issue. In the case we saw in our org, the timeline doesn't line up:
We should investigate:
Links:
The text was updated successfully, but these errors were encountered:
Feels like we can wrap this guy up?
Sorry, something went wrong.
Yeah, I think so, if you're happy with the current workaround. (I consider the \reconnect command a workaround more than a fix, per se)
\reconnect
Then again, this fulfills the stated mission to investigate the bug, so yeah, I'll close it.. :)
kb0rg
No branches or pull requests
After calling the
\zoom
command, a new user was referred to by id instead of username.We suspect this bug is related to an issue filed in the flowdock adapter repo:
However that issue suggests that restarting Hubot will fix the issue. In the case we saw in our org, the timeline doesn't line up:
\zoom
a few hours after Heimdall's new build is releasedWe should investigate:
If restarting fixes the problem, document it for future referencesee testLinks:
The text was updated successfully, but these errors were encountered: