`keybase git gc` on large repo gives `ERROR EOF`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I'm trying to run keybase git gc on a rather large repo (lots of small commits). The process runs for a while, then dies with ERROR EOF. I also noticed it was using a lot of memory while it was running, and I'm pretty sure I saw it get up to 70% memory usage at one point. I've gotten the error at least twice, including immediately after restarting Keybase.
Any idea what would cause this? Is my repo too big, or do I need to run gc more often?
I tried to submit a log with keybase log send right after, but it gave me a network error. Assuming that will be helpful, I'll try again after the next time I get the error, and maybe restart Keybase if I get the error sending the log again. If it still doesn't work, should I zip up the logs to send them directly?
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
Reproduce keybase git gc on a large repository and capture the logs; the report also mentions keybase log send as the submission path, though it failed with a network error. Done means identifying the cause of ERROR EOF and high memory use, then documenting a confirmed fix or workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100