-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
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
Messages posted to threads show up in 1-on-1 channels #153
Comments
Hey @gjabell , thanks for your feedback!
After doing so, I got my friend's reply on the thread channel as expected instead of the 1:1 chat as you experienced. If this is the correct repro for the issue, can you please tell me which commit hash did you build |
Thanks for the quick response! Yes that should be the reproduction steps; it seems it is also an issue if there is not already an open chat with the user, ie anything sent in the thread channel appears instead under the private chat that automatically opens. Here are the relevant debug logs (hopefully removed any private info):
Also worth noting that I am using Weechat, so this might be a client-specific bug. |
Can you help me reproduce this together? Are you on the Gophers slack by any chance? |
@insomniacslk I'd be happy to; I'm not on the Gophers slack but I can join if it's open-registration. |
Yes, it's open, this should let you get an invite, https://invite.slack.golangbridge.org/ |
Should be fixed by #165 |
waiting on @gjabell to confirm before closing this :) |
Seems to work correctly for me now, thanks for all the support! |
Thanks for this project, makes slack much nicer to use than with their web UI :)
It seems that if someone responds to a thread while there is also a 1-on-1 chat open for that same user (for example from /QUERY), then the message they posted to the thread will appear in the 1-on-1 chat rather than under the thread. Note that the thread "channel" still opens, but the messages aren't posted to it.
Can provide debug logs or testing as needed.
The text was updated successfully, but these errors were encountered: