keybase / keybase/client

`keybase chat list-members` responds "incorrect usage" to everything?

Open
#17,250 3 comments 0 reactions 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

$ keybase chat list-members redacted-team-name
Error parsing command line arguments: Incorrect usage.

$ keybase chat list-members redacted-team-name "#general"
Error parsing command line arguments: Incorrect usage.

The documentation says to invoke it as:

keybase chat list-members [command options] [conversation [channel name]]

and what I'm doing seems to match that.

There doesn't seem to be a corresponding chat API method to use instead, either, although one can fake it (awkwardly) by calling read to get the complete chat history, searching for the most recent addedtoteam system message and then taking the union of the owners, admins, readers, and writers fields from that message.

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 the failure with the keybase chat list-members command using both the team name alone and the team plus #general, then compare the behavior with the documented [conversation [channel name]] syntax. Check the related chat API availability and the read workaround described in the issue; done means the command accepts the documented forms and returns the conversation members.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.