Notice how our "git push" fails due to the presence of a file larger than 100MB:
(base) \gh\vid3>git push
Logon failed, use ctrl+c to cancel basic credential prompt.
Username for 'https://github.com': a@b.c
Password for 'https://a@b.c@github.com':
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4/4), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: Unknown error code (err 8)
Wfatal: the remote end hung up unexpectedly
Writing objects: 100% (4/4), 533.93 MiB | 8.86 MiB/s, done.
Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
To overcome this, we install: git-lfs-windows-v2.13.2.exe
And run the following commands:
(base) \gh\vid3>git lfs install
Updated git hooks.
Git LFS initialized.
(base) \gh\vid3>git lfs track "*.*"
Tracking "*.*"
Pattern *.* matches forbidden file .gitignore. If you would like to track .gitignore, modify .gitattributes manually.
(base) \gh\vid3> git lfs track "*.mp4"
Tracking "*.mp4"
(base) \gh\vid3>git add .gitattributes
Note: if we do not do "add & commit" again before "push" again, it results in error:
(base) \gh\vid3>git push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 4 threads
Compressing objects: 100% (4/4), done.
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: Unknown error code (err 8)
Wfatal: the remote end hung up unexpectedly
Writing objects: 100% (4/4), 533.93 MiB | 8.37 MiB/s, done.
Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
After we rename files, add and commit them:
(base) \gh\vid3>git status
On branch main
Your branch is ahead of 'origin/main' by 1 commit.
(use "git push" to publish your local commits)
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
new file: .gitattributes
Changes not staged for commit:
(use "git add/rm <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
deleted: 20210420 174746.mp4
deleted: 20210420_174746.mp4
Untracked files:
(use "git add <file>..." to include in what will be committed)
20210420 174746 (27 MB).mp4
20210420 174746 (521 MB).mp4
If you have low network speed, your "git push" might fail like this:
(base) \gh\vid3>git push
LFS: Client error: https://github-cloud.s3.amazonaws.com/alambic/media/3...2/0f/65/0...f?actor_id=8...7&key_id=0&repo_id=3...1
error: failed to push some refs to 'https://github.com/ashishjainblogger/vid3.git'
(base) \gh\vid3>git push
Uploading LFS objects: 67% (2/3), 98 MB | 105 KB/s
Exiting because of "interrupt" signal.
Additional Note:
My Airtel 4G VoLTE Mobile Hotspot (May 2021) was giving an upload speed of roughly 100 to 200 KB/s.
If everything about the Git-LFS goes right
(base) C:\Users\Ashish Jain\OneDrive\Desktop\gh\vid3>git push
Uploading LFS objects: 67% (2/3), 91 MB | 107 KB/s
A successful attempt logs go like this:
(base) \gh\vid3>git push
Uploading LFS objects: 100% (1/1), 27 MB | 0 B/s, done.
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 4 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (6/6), 713 bytes | 237.00 KiB/s, done.
Total 6 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (1/1), done.
To https://github.com/ashishjainblogger/vid3.git
2*a..e*7 main -> main
[ Ref ]
Pages
- Index of Lessons in Technology
- Index of Book Summaries
- Index of Book Lists And Downloads
- Index For Job Interviews Preparation
- Index of "Algorithms: Design and Analysis"
- Python Course (Index)
- Data Analytics Course (Index)
- Index of Machine Learning
- Postings Index
- Index of BITS WILP Exam Papers and Content
- Lessons in Investing
- Index of Math Lessons
- Index of Management Lessons
- Book Requests
- Index of English Lessons
- Index of Medicines
- Index of Quizzes (Educational)
Monday, May 3, 2021
First time with 'Git LFS' (Git for Large Files)
Labels:
Cloud,
GitHub,
Technology
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment