I
I
its_me_mamoru2018-05-07 06:54:04
git
its_me_mamoru, 2018-05-07 06:54:04

Git gets stuck on writing objects when pushing to Github due to some project files. How to identify problem files?

When trying to upload a project to an empty Github repository, Git freezes for a while at the "Writing objects" step

λ git push -u origin master
Counting objects: 493, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (414/414), done.
Writing objects:  12% (60/493)

In this state, git is idle for about 10-15 minutes, and then Git throws this error:
λ git push -u origin master
Counting objects: 493, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (414/414), done.
remote: fatal: early EOF
fWeatal: The remote end hung up unexpectedly
Writing objects:  80% (395rror: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
Writing objects: 100% (493/493), 3.47 MiB | 9.00 KiB/s, done.
Total 493 (delta 54), reused 489 (delta 54)
fatal: The remote end hung up unexpectedly
Everything up-to-date

To solve the problem, I tried to prescribe the settings `compression = 0` and `http.postBuffer = 524288000` in the repository configuration. Writing object is now stuck on another line
λ git push -u origin master
Counting objects: 493, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (414/414), done.
Writing objects: 100% (493/493), 3.47 MiB | 86.61 MiB/s, done.
Total 493 (delta 54), reused 489 (delta 54) # <-- здесь

But in the end, the same error is displayed, but the output is slightly different.
λ git push -u origin master
Counting objects: 493, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (414/414), done.
Writing objects: 100% (493/493), 3.47 MiB | 86.61 MiB/s, done.
Total 493 (delta 54), reused 489 (delta 54)
remote: fatal: early EOF
featal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
rror: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
Everything up-to-date

The error is repeated on the other two machines.
Apparently, the plugging occurs on some of the project files. I tried uploading the project to the repository (another one created for testing) in parts, and some portions of the files are loaded normally. But which files are causing problems, I can't figure out. The gag mostly occurs when loading images, font files, and some CSS files. But they all work fine, open, are perceived by the browser.
How to see which specific files are problematic? Or how to get Git to push them to Github as they are now?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
A
asdz, 2018-06-06
@asdz

Try changing the channel to a physically different one, it could be a network problem.
Try enabling the GIT_TRACE_PACKET flag.
Try to work with another repository, which obviously does not contain problematic files.
Try to work with this repository on another computer.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question