Failed to open chat conversation: TLF name 2
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm trying to open this 'unread' chat conversation but it gives some errors.
On the command line:
$ keybase chat ls
...
[2] (unverified) cfle... [???] no valid message in the conversation
$ keybase chat read 2
▶ ERROR failed to open chat conversation: TLF name 2 is in an incorrect format
On the GUI:
error unboxing chat message: box.Open failure; ciphertext was corrupted or wrong key
my log id: b3dbbe6dae8a93cc4ceabe1c
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with keybase chat ls and keybase chat read 2, then compare it with the GUI unboxing error using log id b3dbbe6dae8a93cc4ceabe1c. Trace the conversation-opening and message-unboxing path to determine why the conversation has an invalid TLF name or corrupted ciphertext; done means the affected conversation opens successfully in both interfaces.
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