No TLF name specified
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I tried to create a new Keybase chat message in an existing conversation this morning, just after installing Keybase for Mac last night (running under latest version of OSX Sierra), and got the following error message: "Error: No TLF name specified". The messages that followed all referred to the file /Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js.
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 error while creating a message in an existing Keybase conversation on the Mac app, then inspect /Applications/Keybase.app/Contents/Resources/app/desktop/dist/index.bundle.js and the surrounding error output. Done means identifying and correcting the cause so a new message can be created without the “No TLF name specified” error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100