Menu
I downloaded and installed Git Large File Storage. Now I'm trying to get lfs files from the existing repository in github (not mine). I tried:
git lfs clone https://github.com/xxx/xxx
then in my local just cloned repo:
git lfs fetch --all
git lfs pull
I also tried the same but without "lfs".
The repository is cloned but for all lfs files always this error is shown:
[301582dabd8c6ac7bdf626c7e4a1d64c8f9665b65b6334b44642bdfb78054575] Object does not exist on the server: [404] Object does not exist on the server
and then:
error: failed to fetch some objects from 'https://github.com/xxx/xxx.git/info/lfs'
As a result, instead of real large files, their small pointers that can be seen in GitHub itself are cloned.
At the same time this command:
git log --all -p -S 301582dabd8c6ac7bdf626c7e4a1d64c8f9665b65b6334b44642bdfb78054575
gives the following results:
commit 36c7dba69de90d99f0c305fce13a598b8f06b443
Author: xxx
Date: Wed Sep 11 18:01:25 2019 +0200
Add embeddings
diff --git a/embeddings/wikipedia/0.pkl b/embeddings/wikipedia/0.pkl
new file mode 100644
index 0000000..5ee94da
--- /dev/null
+++ b/embeddings/wikipedia/0.pkl
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:301582dabd8c6ac7bdf626c7e4a1d64c8f9665b65b6334b44642bdfb78054575
+size 588838774
I am not very confident user of GitHub, especially, of LFS. So, the question is: am I doing something wrong or does it indeed mean that the files do not exist on the server?
648
Git LFS (Large File Storage) is a Git extension developed by Atlassian, GitHub, and a few other open source contributors, that reduces the impact of large files in your repository by downloading the relevant versions of them lazily.
remote: GitLab: LFS objects are missing. Ensure LFS is properly set up or try a manual "git lfs push --all". The solution was to disable Git Large File Storage (LFS) in the gitlab project settings. Settings > General > Visibility, project features, permissions > Expand > Git Large File Storage (LFS) And it is faster than the other answer.
This makes our task failed. Since this is not a real error, why does git lfs return 2? Missing an object on the server indicates a failure to fetch all objects correctly. For pushes, you can use the 'lfs.allowincompletepush' option, but there is currently no equivalent for fetches.
404 - The object does not exist on the server. which would be an invalid error when git lfs push -ing, but would indicate a missing object when you are running git lfs fetch. we got the object Not found [404] error when we were running the command 'git lfs fetch --all'.
This isn't an issue in Git LFS: the server said it didn't have the object and there's nothing we can do to make it hand it over. It may really have the object and be stating that falsely, or it may really not have it at all. But regardless, you'd need to reach out the server maintainer and talk to them about it.
This error message is an HTTP 404 Not Found error. Essentially, that means that Git LFS tried to pull down the file, but it wasn't there. In all likelihood, the user did not upload it properly, possibly because they didn't run git lfs install. If they had run that command, the pre-push hook installed in their repository would have pushed the files to the server before the Git objects were uploaded.
Since the files weren't uploaded, there's no way for you to download them. You'll have to ask the author to run git lfs push --all in their repository to upload them to the proper location so they can be downloaded.
107
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
