Cloning encrypted git repository failed with "bad object"
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I tried to git clone my repository from Keybase and got this error:
Cryptographic cloning: (100.00%) 1.70/1.70 MB... done.
fatal: bad object 4d0eab67156ac53dbdf775fdaf18469215343ee4
fatal: remote did not send all necessary objects
my log id: 7c5168e63ec5c0077cbe461c
This was on Windows running git through cygwin, which may or may not be a factor.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the encrypted clone on Windows through Cygwin and inspect the failure using log ID 7c5168e63ec5c0077cbe461c. Compare the clone behavior and object-transfer errors with a non-Cygwin environment; the work is done when the repository clones without the “bad object” or missing-object errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100