keybase / keybase/client

Unable to see chat channels on keybasefriends

Open
#19,149 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

This is related to an issue I am having on keybasefriends#general:

xistence@Alexandra ~ % keybase chat list-channels keybasefriends
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
▶ WARNING Bad subkey: openpgp: invalid data: Subkey wasn't signed; expected a 'binding' signature
Listing channels on keybasefriends:

#general [if you're in Europe, check out the new @europe team] (created by: chris on: 2017-09-06)
#slack-admins [a group for discussing possible ways a team might switch from Slack to Keybase. Join if you administer a Slack team.] (created by: chris on: 2019-04-12)

I am unable to see the additional channels that exist, as another user was kind enough to show them to me.

Is this a caching issue or something else?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing keybase chat list-channels keybasefriends and compare its output with the additional channels reported by another user. Trace the chat list-channels command and its channel-listing path; done means the command reliably displays all channels the user can access, without the reported omissions.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.