Panic: error uploading files #487
Comments
|
What version of Git LFS? |
|
git-lfs/0.5.2 (GitHub; darwin amd64; go 1.3) ConcurrentTransfers=3 |
|
Ah, this was reported in #317. I thought it'd be taken care of by v0.5.2, but apparently that's not the case. Is it happening every time you try to push? |
|
Based on your |
|
No it isn't happening every time. I'm currently uploading a large set of large files and it's been working fine for the first 7,000 of them, this time around. I haven't worked much with |
|
Ok try this. If compiling this doesn't work, don't spend any time troubleshooting that part unless you care about having a functioning Go setup. I'd be happy to help if that's the case. |
|
The bootstrap script is failing with: |
|
I'm also running into another error. Yesterday evening the push of a large file set failed (our internet connection may have dropped), producing this error: And now when I try to push it stalls before it can upload the first one and eventually produces this error: |
|
More details related to the issue in the previous comment. While running and subsequent checks show that the |
|
@joelfgs Try this: https://github.com/github/git-lfs/releases/download/v0.5.1-tracing/git-lfs.zip This is what I'm using to QA stuff for the release. It should fix the original panic that you experienced for good. For your second error, can you run Is the problem still happening after your internet connection was restored? Also, try adding |
|
TL;DR - Thanks it's working (I think), but an unexpected prompt for authentication appears to have cancelled the whole shebang. Thanks, I've installed lfs from the zip file. The fsck reports everything is OK so I kicked off another attempt at pushing everything yesterday, using I'm guessing that this activity is what, in the I groggily hit Enter a couple of times in my terminal. I should have only done it once because after the first one I was prompted for a Running The |
|
@joelfgs If you want to give me some more details at support@github.com, I can double check to see if those files made it. If your client successfully made the "verify" API call, you won't have to re-upload them again. If your client only made a successful file upload to S3, I can manually verify them on the server. Also, you may have better luck using HTTPS instead of SSH for now, since the current API is so chatty. Improving this is a big part of the push to v0.6.0. There will be way fewer SSH calls and |
|
Great, yeah after switching over to HTTPS everything was much faster. The push finally finished successfully, thanks for your help! |
Related to #317 perhaps. When uploading on OSX it threw the error below and seemed to get stuck. Here's the go env:
Here's the error:
The text was updated successfully, but these errors were encountered: