0
I have some projects hosted on Azure and I use git for versioning, they all worked well but from one moment to another one of these repositories started to give problem and does not end the push (but only with me, with other people of the project works normally. I already deleted the project and downloaded again from scratch, but it didn’t work.
There are two kinds of mistakes:
Error 1 (processing stops in "Total" and nothing happens, neither ends nor error):
$ git push
Enumerating objects: 1167, done.
Counting objects: 100% (1146/1146), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1115/1115), done.
Writing objects: 100% (1115/1115), 292.52 MiB | 16.12 MiB/s, done.
Total 1115 (delta 549), reused 76 (delta 0), pack-reused 0
Error 2 (pass this point of the total with error 503):
$ git push
Enumerating objects: 1167, done.
Counting objects: 100% (1146/1146), done.
Delta compression using up to 8 threads
Compressing objects: 100% (1115/1115), done.
Writing objects: 100% (1115/1115), 292.52 MiB | 16.12 MiB/s, done.
Total 1115 (delta 549), reused 76 (delta 0), pack-reused 0
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
I’ve followed a lot of things that could work, but none of them worked, I increased the http.postBuffer
both globally and only for the project, nothing solved.
I also tried to download the Fork and push through the graphical interface, even though it showed no error, stayed almost an hour processing the push and canceled.
And I’ve got three local commits here that can’t be lost because they involve a lot of work, someone knows how to get out of it?
EDIT Print with git status and error:
because of error 503 I would say you are having network problems (the message already shows this "Unexpected Disconnect while Reading sideband Packet"). At the time of terminating the failed command, this happens to me sometimes in gitlab, either by too many connections or other network problem.
– Ricardo Pontual
The strange thing is that all other repositories work normally, on the same network, same computer, and this 5003 error is very difficult to happen, 90% of the time it only stops in the "Total" same, but I will try in another network as soon as possible
– Gabriel Queiroz Schicora
I tested now in another network, the same, stands still in "Total".
– Gabriel Queiroz Schicora