Git clone fails halfway through
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hello,
I have moved a ~600MB repository with my Mac with success, however, when I try to clone that same repository on my Windows machine, the git clone stops halfway through with no apparent reason. The only thing that I noticed might be a problem is a rampant memory usage by the git-remote module. Here is how the console looks like after a failed clone:
C:\Users\WallE256>git clone keybase://team/ichb_ftc_dev/robovamps_app
Cloning into 'robovamps_app'...
Initializing Keybase... done.
Syncing with Keybase... done.
Counting: 599.43 MB... done.
Cryptographic cloning: (47.31%) 283.57/599.43 MB...
C:\Users\WallE256>
Let me know if I can provide any additional information.
Thanks.
my log id: b9d9b53eb2ca0c0c01d9e71c
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 git clone keybase://team/ichb_ftc_dev/robovamps_app on Windows using the reported log id and observe memory use during cryptographic cloning. Start by tracing the git-remote component mentioned in the report; the issue is done when the repository clones past the reported 47.31% point without failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100