We’re seeing intermittent failures on git clones from our pipelines:
error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
Would appreciate an update on this from the gitlab team through the status page/alerts as this is hindering our work by causing failed builds.
I checked out a relatively small repository within a few seconds. I have a 4.2GB repository that is taking far longer, but that could be more due to the size, and is so far 6 minutes in and 42% complete. So difficult to say. Could just be problems with shared runners if only pipelines affected. Or potentially even location-specific depending on where you are in the world.
Unfortunately, free support doesn’t have any priorities. Only paid support gets a priority so assuming that paid customers have reported this, then I expect it will be resolved soon. As for us free users, nothing we can do except wait.
Then as a paying customer it’s far quicker for you to get support from the Gitlab ticketing system. This forum is pretty much for the community and therefore a quick response isn’t guaranteed here. Via the Gitlab tickets is the only way to guarantee a quick response for paid clients.
I am just a community member, not Gitlab staff, so have no influence over anything