Git push in Cygwin gets stuck uploading LFS objects at 0% and then times out #5870
Comments
|
Running |
|
Likely related to #2791 since I disabled locks-verify to fix a previous issue preventing me from pushing my first LFS file a few weeks ago. |
hashimaziz1
changed the title
|
Hey, I'm sorry you're having trouble. I tried to replicate this but I only have success when pushing to GitHub right now, using an SSH endpoint, and testing with Git LFS objects in the pushes. As this project is only for the Git LFS client, I would suggest reaching out to GitHub's Support team if you continue to experience problems. Two things I happen to notice, in case they have any utility in diagnosing the problem with GitHub's people. One is that your version of Git LFS is 3.3.0 and mine is 3.5.1; there are a number of SSH-related changes between those versions, but, that said, I don't think any of them would be related to your disconnection problems. The other detail is that from the IP address in your logs ( And, of course, we always recommend removing any monitoring or firewall software you have installed locally, to make sure that's not interfering in some way. Regardless, good luck and I hope you get the issue resolved! Let us know how it turns out. |
|
I was able to work around this for now by adding In case anyone does have an interest in finally getting this fixed, I have a feeling this is something to do with trying to use an SSH identity file when no ASKPASS binary is set (Cygwin doesn't come with one). Here are a few virtually identical issues that have also never been resolved: #2349, git-for-windows/git#1613, #1843, #3216. |
|
I'm glad you found a working configuration which helps mitigate your problem! We're always interested in trying to resolve issues. The key challenge for us is that we need a reproducible test case in order to be able to diagnose something; in this particular case, from your initial description, an SSH issue on GitHub's side seemed most likely to me, particularly as I wasn't able to reproduce the problem myself. As you're obviously expert with Windows development, if you're able to pin down the exact cause of the issue, that would be most welcome! Patches and PRs are also always greatly appreciated. In the meantime, I'll mark this as a bug and put it into the backlog, and if anyone is able to look at it before we're able, so much the better. Thanks again for your detailed report, and I'm glad you've got something working for you now, even if it's a workaround. |
For the past few hours I've been unable to push changes to my GitHub origin answer because it hangs indefinitely - the only output I get is:
This is definitely not a network issue as similar issues have been closed for, because the network is working fine when LFS is not involved.
Running with
GIT_TRACE=1 GIT_TRANSFER_TRACE=1 GIT_CURL_VERBOSE=1 git pushgives the following:2:24 is the point at which I hit Ctrl+C and the subsequent commands are always the same no matter when I do so, indicating no actual progress is being made. This seems to be an authentication issue, and I do use an SSH key file with a passphrase, but running with the wrapper script from #3779 (pointing to
/usr/bin/sshinstead of Windows Git) makes no difference.Letting the command run all the way until the end eventually terminates with:
System environment
Cygwin running on Windows 10,
which sshshowsusr/bin/sshandssh -Vshows:Output of
git config -lOutput of
git lfs envAdditional context
I had previously committed the 130MB file and forgotten to track it with
git lfs track, then rangit lfs trackand latergit lfs migrate, which successfully rewrote the refs for those commits and added the file to.gitattributes.git lfs ls-filesgives me the two files I expect to be tracked with LFS (the first one was pushed a few weeks ago without issues).Would really appreciate some help here because I'm out of ideas and I'd really like to be able to push my changes sometime soon.
The text was updated successfully, but these errors were encountered: