Files get skipped, repository or object not found. #1151
Comments
|
Skipped files means the server already has it, and you don't need to upload it again. I need more details to troubleshoot this though:
The easiest way to find this is by running: $ git remote -v
$ GIT_TRACE=1 git push ....If this is for a GitHub repository, you can send me the details privately to https://github.com/contact. If it's hosted elsewhere, you may be better off contacting their support. If you're just completely stuck, you can add the output to this issue, or send it to me privately, and I'll do my best. |
|
That makes sense, but why is it treated like an error? I'm using SmartGit and SourceTree and both stop the push when the files get ignored and print it as an error. Could the issue be at the server? It's a GitLab server. Git LFS version is 1.1.2 but I'm not sure if SourceTree uses the locally installed version or it's own. There are thousands of skipped objects. I guess it's due to an aborted push earlier, but I still don't understand why it doesn't just ignore the warnings and keep pushing.. I'm not completely stuck as we still have the repository at Perforce left. The reason we tried to move to GitLab is because GitHub doesn't support such a large repository and we have a lot textures and sounds. It's a shame but I understand why the limitation is there. Thanks for your time Rick! |
Skipped files aren't an error. That's totally normal. I wonder if we should even show that info :) The response "Repository or object not found" has to do with an http response from the lfs server. You'll have to work with Gitlab on that. If you want to post the info that I requested, I can help nail down what specific questions to ask them. |
|
I really appreciate the offer, thanks a lot! I managed to track this down.. we're not using HTTPS which LFS defaults to. I tried to force HTTP by issuing the following command:
And now it's pushing! :) One question though: are you sure skipped files always mean the files exist on the server? What about when the connection is down? These files couldn't possibly have existed on the server to begin with because there was no connection? In any case, thanks again! |
|
Wow, you should not be using HTTP :) Glad you got it to work at least. If the connection is down, the |
|
Just wanted to get something up and running so I can test it. =) LFS is at 1.1.2. It's the initial push. The push failed with a huge stacktrace:
Wow that's huge, sorry. Let me know if I should trim it down and put up a link instead. |
|
Yikes, that looks like a memory issue on your system. How's your memory utilization while the push is running? Initial pushes typically scan the entire history of each branch to push. Since your branches all have common ancestors. You can see this when you push by looking for multiple "Git LFS" prompts: In my completely fabricated scenario above, the same 11197 objects are being uploaded 3 times (for 3 different branches). Git LFS v1.2 has a major optimization on initial pushes here, where those duplicate objects in the same |
|
Makes sense, thanks! I guess I'm just confused why those warnings are gone after the change to HTTP. I'm happy with the additional progress though. :) Memory is 78% free on the server and 39% free on the client. I'll try with 1.2 tomorrow incase that helps. Edit: Same result. Memory usage is pretty stable and never goes above 500MB. |
You mean this error from your initial post?
That depends on how your server is configured. If looks like it just doesn't support LFS properly.
Is that the |
|
It just dies and shows the runtime stack without showing any info about the objects processed. Oh and those numbers are for the client and the server, not the individual processes. Would love to try this out on GitHub but my repository is too large, hehe! |
|
On BitBucket the same repository pushes just fine. |
|
Cool, glad you found a workaround. Sorry we couldn't help you, nothing you posted points to a server side issue. |
Upon pushing to a remote, LFS skipped all of my files:
Git LFS: (16 of 11213 files, 11205 skipped) 1.22 MB / 1.42 GB, 1019.20 MB skippedAnd then stops with the following error:
I'm now blocked from pushing to the repository. Any idea what's going on?
The text was updated successfully, but these errors were encountered: