BlueRose/BlueRoseNote
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2024-09-02 23:48:03

Browse Source
This commit is contained in:
BlueRose 2024-09-02 23:48:03 +08:00
parent eafffd57e4
commit cbde373033
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
03-UnrealEngine/Gameplay/Gameplay/Git & LFS 笔记.md
View File

@ -118,9 +118,27 @@ git config --global lfs.concurrenttransfers 1
### 服务器上不存在 ### 服务器上不存在
解决方案：上传指定lfs文件：git lfs push origin --object-id [ID] 解决方案：上传指定lfs文件：git lfs push origin --object-id [ID]
### LFS objects are missing on push[](https://docs.gitlab.com/ee/topics/git/lfs/troubleshooting.html#lfs-objects-are-missing-on-push "Permalink")
GitLab checks files on push to detect LFS pointers. If it detects LFS pointers, GitLab tries to verify that those files already exist in LFS. If you use a separate server for Git LFS, and you encounter this problem:
1. Verify you have installed Git LFS locally.
2. Consider a manual push with `git lfs push --all`.
### 强制上传LFS ### 强制上传LFS
git lfs push origin --all git lfs push origin --all
### I/O timeout when pushing LFS objects[](https://docs.gitlab.com/ee/topics/git/lfs/troubleshooting.html#io-timeout-when-pushing-lfs-objects "Permalink")
If your network conditions are unstable, the Git LFS client might time out when trying to upload files. You might see errors like:
```
LFS: Put "http://example.com/root/project.git/gitlab-lfs/objects/<OBJECT-ID>/15":
read tcp your-instance-ip:54544->your-instance-ip:443: i/o timeout
error: failed to push some refs to 'ssh://example.com:2222/root/project.git'
```
To fix this problem, set the client activity timeout a higher value. For example, to set the timeout to 60 seconds:
```
git config lfs.activitytimeout 60
```
# 引擎Content管理 # 引擎Content管理
.gitignore文件中添加 .gitignore文件中添加
``` ```