This article has participated in the Denver Nuggets Creators Camp 3 “More Productive writing” track, see details: Digg project | creators Camp 3 ongoing, “write” personal impact.

One, encounter problems

When submitting a project, I stopped to this screen for a long time…

Wait for an error, tell me to submit failed…An error in the original

git -c diff.mnemonicprefix=false -c core.quotepath=false –no-optional-locks commit -q -F C:\Users\25924\AppData\Local\Temp\jh2zoq3f.4ns

git -c diff.mnemonicprefix=false -c core.quotepath=false –no-optional-locks push -v –tags –set-upstream origin master:master POST git-receive-pack (88465735 bytes) error: RPC failed; curl 55 Recv failure: Connection was reset fatal: the remote end hung up unexpectedly fatal: The remote end hung up unexpectedly Pushing to http://172.28.60… Everything up-to-date completes with an error, see above.

It has been good before, but suddenly it is not good, I am very confused.

Two, try to solve

Searched the Internet to have a few kinds of solutions, although did not solve my problem, in case you can solve the problem

1. Use the SSH key

Open: tools -> Options -> General -> SSH ClientChange to OpenSSH and select your own SHH key above.PS: ANYWAY, I tried it. It didn’t work. I used the default, and neither of the two options solved the problem I encountered.

2. Deselect the proxy server

Open method: [Tools -> Options -> Network]

PS: I originally did not tick ah, woof ┭┮﹏┭┮…

3. Modify git configuration to increase httpBuffer

See this before deciding whether to try this operationOpen command line mode at SourceTree:

Type the following command to view your Git configuration:

git config -l
Copy the code

Git config -l to check whether the buffs have been buffed successfully, and then try pushing them again.

git config --global http.postBuffer 524288000
Copy the code

Later, I found that: this buff error is: RPC failed; curl ==56== Recv failure: Connection was ==reset==. And I encountered an error that made RPC failed; Curl ==55== Send failure: Connection was ==aborted==

Third, solve problems

The same is true for pushing results using command line mode, == this indicates that SourceTree is not the problem ==

Because it was used before, the submission push somehow did not work this time, so I guess there may be something wrong with the content submitted this time.

According to this speculation I re-cloned a new project to the local, and then casually modify a text, and then temporary save, push at one go, no problem at all;

This time it can be confirmed that there is something wrong with the content I push this time. I push the normal Unity project logic modification and submit the Android project exported by Unity. I suspect that there is something wrong with the project content submission.

GitLab using SourceTree’s hosting address above, and then I re-code cloud upload the same project, there is no problem.

Preliminary conclusion: When GitLab uploads large files, it takes a long time and is prone to network interruption, which leads to this situation. Solution 1: Upload large files in batches. Solution 2: use domestic code to host the code cloud.

If you have different views, welcome to leave a message to clarify; If you have a similar problem, please leave a comment in the comments section to help other students.