keybase / keybase/client

Duplicate #general channel (sometimes a blank # channel) when switching to/from big team

Open
#24,163 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

I just got this same issue this evening. I created a team (with no channels) a month ago. I changed it to a big team at some point and then switched it back. Now, I made it back into a big team and it created another #general channel (on my Mac) (but I think under Windows it appeared as a blank channel (#). I was able to do a 'keybase chat rename-channel teamname general' and it showed the two #general channels. Then I was able to rename the bad one and then delete it. That got me back to square one apparently.

But, I want to make sure I'm starting this team with a "clean slate" now that I had these issues because I tried it again, and it happened again; and then I removed the channel again. Any ideas? I did already send my logs this evening ("keybase send logs").

my log id: 39fac483d05cb0a95ea31f1c

I might have "fixed" the issue, but unsure. I submitted another set of logs using log id: 33d63049f36a21d34584df1c

So this could be a "before" and "after" log set. I'm not positive it's fixed in the latter yet.

Thanks for the help!

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the reported sequence of creating a team, switching between regular and big team, and checking its channels on Mac and Windows. Review the two submitted log IDs and use `keybase chat rename-channel` to inspect channel names; done means the transition produces one valid #general channel without a blank duplicate.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.