-
Notifications
You must be signed in to change notification settings - Fork 60
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
Unable to /join a public channel or /part any channel from IRC #479
Comments
Might be related to #237 |
wrt to /part => /join should work.. run with |
Ah sorry I overlooked the partfake setting. About joining channels, we're using MM 6.x but then I already set defaultTeam to our current sole team.
Same when using #myteam/some-existing-public-channel. Cheers |
Well, this shows that it cannot find the channel. Redacting too much information makes it harder to debug. As a workaround just join the channel using the webbrowser, this should be a one-time action. |
The team name is nothing special, just "canonical". The channel itself is public and consists of letters and dashes only (and public information but then I did not see the point in keeping the name on this bug report). Afaik, it has never worked for at least 2 people (including myself), on any channel we wanted to join. |
What mattermost version? |
Mattermost Version: 6.6.0 |
I can confirm this is the case and seems to do with the
Now on trying to join, I get this:
Even with team name it's failing:
|
Cowboying out channelID as follows:
Works. |
The issue is with |
Maybe rather than loop through list of all channels, use the Mattermost API |
It's probably done this way so we have a cache instead of sending too many requests to mattermost.
|
I think this is a server side issue then:
With that query directly via the API, I only get 200 results returned. This is with MM 6.6.0. I think the workaround of using GetChannelByName is needed here rather than get all available channels and try walk through? With GetChannelbyName, we're also able to join private channels. |
Or perhaps use the cache and fall back? So:
|
Upstream change - 42wim/matterbridge#1909 We can re-vendor these changes if/when it's accepted in matterbridge upstream. |
Maybe similar upstream bug mattermost/mattermost#20810. But its old, I'll file a new one tomorrow. |
https://github.com/mattermost/mattermost-server/blob/master/web/params.go#L17
I think I got 357 channels earlier was because it combines both:
That's Channels and MoreChannels. |
Thanks for digging in this @hloeung |
Thanks to @hloeung this is now fixed in master |
Hi,
When I try to join a specific public channel from my IRC client, I get this:
Same if I try using ~ instead of #.
When I join the same channel from WebUI, channel being public and not invite only, I properly get a:
Also, when I /part a channel from my IRC client, it behaves as if I left the channel, but then I'm still on said channel when I connect to mattermost WebUI. This is the raw log from hexchat:
Let me know if there's anything I missed or if you need more details.
Thank you!
The text was updated successfully, but these errors were encountered: