Getting git-remote-keybase error: (1) Directory split-clerk is not empty and can't be removed on both Mac and Windows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I have a Keybase git Personal repository that I have successfully used on both Windows and Mac before. This week whenever I try a git pull or git push, I get an error:
Getting git-remote-keybase error: (1) Directory split-clerk is not empty and can't be removed on both Mac and Windows.
I've searched my drives and have no directory named "split-clerk".
I get the same error when I attempt to clone other older repositories.
Keybase git is now unusable, and I fear that I've lost access to all my repositories.
Windows log ID from keybase log send: 96b0e326c9d565d0a287311c
Mac log ID from keybase log send: 231755b666d9150eb92b5e1c
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 git pull, git push, and cloning an older repository on the affected platforms. Review the Windows log ID 96b0e326c9d565d0a287311c and Mac log ID 231755b666d9150eb92b5e1c, then trace the git-remote-keybase handling of the split-clerk directory. Done means these operations no longer fail and existing repositories remain accessible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100