keybase / keybase/keybase-issues

warn: No config file found; tried '/home/me/.config/keybase/config.json'

Open
#1,108 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

with the CLI, I always get that error warning. Do I have to worry?
What is it good for?
Ok, just for curiosity, I did
touch /home/me/.config/keybase/config.json
but thereafter, it refused service altogether :(

error: Invalid json in /home/hauser/.config/keybase/config.json: SyntaxError: Unexpected end of input
error: Unexpected end of input

keybase config foo bar

fixes it, but hmm...
https://github.com/keybase/keybase-issues/issues/908

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 warning for /home/me/.config/keybase/config.json and the failure caused by creating an empty file. Review the CLI behavior around keybase config foo bar; done should mean missing or empty configuration is handled consistently without refusing service.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.