keybase / keybase/keybase-issues
"Keybase: Out of space" issue
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I have 2 private repos (and no other repos - either individual or team).
Both of these, I recreate from scratch - since I dont require history - from time to time. At present, local disk sizes are approx 1GB and 514M
I also periodically run keybase git gc <repoName> command - which presumably "trims" the repo size.
In spite of all this, I have been getting a notification stating "Keybase: Out of space" in the past couple of hours. The reported size in the notification is 107.7 GB - whereas the local repo sizes are much smaller. What can I do to trim the remote? I have also tried deleting the old repo and recreating one with the same name (ie from scratch) - via the Keybase app on Mac OS.
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 reviewing the reported keybase git gc <repoName> command and the Keybase app on Mac OS, then trace how remote repository storage is accounted for. Done means explaining the 107.7 GB discrepancy and identifying a documented or verifiable way to reclaim the remote space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100