Keybase Sync Command Fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Normally one uses the keybase fs commands where the filesystem is mounted (*nix distributions mount it in /keybase while Windows uses K:\). On the Mac a recent change means that you cannot have folders in the root tree so /keybase doesn't work and now uses /Volumes/Keybase.
When using the command to sync a folder you get this:
keybase fs sync enable /Volumes/Keybase/[something]/[something]
▶ ERROR Invalid remote path
However, if you instead say:
keybase fs sync enable /keybase/[something]/[something]
It works fine.
Using macOS Catalina and the latest Keybase version.
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 at the keybase fs sync enable command and its remote-path validation, comparing the reported /Volumes/Keybase/... and working /keybase/... paths on macOS. Done means the sync command accepts the current macOS Keybase mount path without returning Invalid remote path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100