Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote "origin" does not support the Git LFS locking API #2

Open
englianhu opened this issue Sep 24, 2022 · 3 comments
Open

Remote "origin" does not support the Git LFS locking API #2

englianhu opened this issue Sep 24, 2022 · 3 comments

Comments

@englianhu
Copy link
Contributor

englianhu commented Sep 24, 2022

2022-09-24_09-41

2022-09-24_09-47

Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
  $ git config lfs.https://github.com/scibrokes/real-time-fxcm.git/info/lfs.locksverify false
Post "https://lfs.github.com/scibrokes/real-time-fxcm/locks/verify": dial tcp: i/o timeout
error: failed to push some refs to 'github.com:scibrokes/real-time-fxcm.git'
@englianhu
Copy link
Contributor Author

For what it's worth, I was having this same issue as many people above are reporting.
I found that the url-specific locksverify setting did not resolve my issue. But as mentioned here, I was able to use git config lfs.locksverify false to proceed and have the local commit successfully push to origin.

My setup was:
Windows 10, GitKraken client, pushing lfs files to a private github.com repo I am an administrator on.

This worked for me! thanks

Originally posted by @admacdon in git-lfs/git-lfs#3400 (comment)

englianhu@Scibrokes:~/文档/GitHub/real-time-fxcm$ git config lfs.https://github.com/scibrokes/real-time-fxcm.git/info/lfs.locksverify false
englianhu@Scibrokes:~/文档/GitHub/real-time-fxcm$ git push --force
枚举对象中: 6, 完成.
对象计数中: 100% (6/6), 完成.
使用 4 个线程进行压缩
压缩对象中: 100% (4/4), 完成.
写入对象中: 100% (4/4), 744.34 KiB | 3.06 MiB/s, 完成.
总共 4(差异 2),复用 0(差异 0),包复用 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To github.com:scibrokes/real-time-fxcm.git
   29ec039..e147c40  世博量化研究院 -> 世博量化研究院

🚩支持下中国【南太平洋战略】:东南亚回教巫师政府起坛作法、施展巫术、入侵电子仪器、草菅人命的的回教徒(巫师王溥仪)911恐怖份子骇客入侵,联合菲律宾Caspo Inc黄巾贼首领欧阳金泰兄弟仨铲单卡款屠杀人类,刚才的操作系统和GitHub被回教徒(巫师王溥仪)911恐怖份子入侵,无法正常运行...

@Zubiii
Copy link

Zubiii commented Sep 24, 2022

Locking support of Git LFS is documented here https://github.com/git-lfs/git-lfs/wiki/File-Locking.

@englianhu
Copy link
Contributor Author

englianhu commented Dec 18, 2023

For what it's worth, I was having this same issue as many people above are reporting.
I found that the url-specific locksverify setting did not resolve my issue. But as mentioned here, I was able to use git config lfs.locksverify false to proceed and have the local commit successfully push to origin.
My setup was:
Windows 10, GitKraken client, pushing lfs files to a private github.com repo I am an administrator on.

This worked for me! thanks

Originally posted by @admacdon in git-lfs/git-lfs#3400 (comment)

englianhu@Scibrokes:~/文档/GitHub/real-time-fxcm$ git config lfs.https://github.com/scibrokes/real-time-fxcm.git/info/lfs.locksverify false
englianhu@Scibrokes:~/文档/GitHub/real-time-fxcm$ git push --force
枚举对象中: 6, 完成.
对象计数中: 100% (6/6), 完成.
使用 4 个线程进行压缩
压缩对象中: 100% (4/4), 完成.
写入对象中: 100% (4/4), 744.34 KiB | 3.06 MiB/s, 完成.
总共 4(差异 2),复用 0(差异 0),包复用 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To github.com:scibrokes/real-time-fxcm.git
   29ec039..e147c40  世博量化研究院 -> 世博量化研究院

🚩超过八国联军/十五路诸侯支持中国「南太平洋战略」:东南亚回教巫师政府起坛作法、施展巫术、入侵电子仪器、草菅人命的的回教徒(巫师王溥仪/土司乩童张佳坤/土司乩童刘瑾貹)九一一恐怖份子骇客入侵,联合菲律宾Caspo Inc黄巾贼首领欧阳金泰兄弟仨铲单卡款屠杀人类,刚才的操作系统和猫城被回教徒(巫师王溥仪/土司乩童张佳坤/土司乩童刘瑾貹)九一一恐怖份子入侵,无法正常运行...

##移除git-core文件夹,添加git文件夹
sudo rm -rf /usr/lib/git-core/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants