Unexpected Git error on GitHub Actions: RPC failed; HTTP 408 curl 18 HTTP/2

[jeanjerome]

Select Topic Area

Bug

Body

Hello everyone,

Since yesterday, GitHub Actions have been returning errors of the following type when deploying to GitHub Pages:

Deploying to scalastic/scalastic.github.io on branch gh-pages
Deploying to ***github.com/scalastic/scalastic.github.io.git
...
Initialized empty Git repository in /github/workspace/build/.git/
[master (root-commit) 4089974] jekyll build from Action c4440fef66d42f3d7031f4ca87911d4a24c14532
 1205 files changed, 25677 insertions(+)
 create mode 100644 .nojekyll
 create mode 100644 404.html
 create mode 100644 CNAME
...
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

Is there a problem or a change in the GitHub Pages deployment process?
Thank you for your response.

[jeanjerome]

I you want to have a look to the complete logs: https://github.com/scalastic/scalastic.github.io/actions/runs/5008728644/jobs/8976906598

[Jason2866]

It is not a fix! It is a workaround. Thx for the workaround.
BUT the issue hits a lot of GH Actions and it is not the solution to add workarounds everywhere.
Github needs to find the reason and fix it or tell officialy what changes are needed.

[jeffreytse]

@Jason2866 You're right, but before the final official solution coming out, it's a good workaround so call "fix" to settle the issue effectively.

[nihaals]

I think the rationale for not wanting it to be marked as the answer is so GitHub is more likely to see this discussion as opposed to assuming it is "solved" so it is investigated sooner (assuming they haven't investigated based on support tickets and possible server logs).

[aminvakil]

@nihaals Thanks, exactly!

[Sanni-Damilola]

jobs:
your_job:
runs-on: ubuntu-latest
env:
GIT_HTTP_TIMEOUT: 300 # Set a higher timeout value (e.g., 5 minutes)
steps:
- name: Your Git action step
# Your Git-related actions here

[mkjsix]

We have the same error here:
https://github.com/SoftInstigate/restheart-website/actions/runs/5013979152/jobs/8987705668

The error log ends with:

...
 create mode 100644 use-cases/rest-api.html
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date

The workflow is:
https://github.com/SoftInstigate/restheart-website/blob/master/.github/workflows/jekyll.yml

[aminvakil]

Same here:
https://github.com/aminvakil/aur/actions/runs/5009690513/jobs/8988928436#step:11:177
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset

[BryanSchuetz]

Having the same issue

[JunchengXue]

Having the same issue

[BryanSchuetz]

Have tried a number of things to get around this issue but nothing seems to work. I though maybe the repo was to large, but reducing the size and trying again hasn't had an impact. This action has been working many times a day for months with no issue, until yesterday... not sure how to address short of just completely rewriting the workflow, but even then I'm not sure the same thing still won't happen.

[EverettBerry]

We are having the same issue. Reduced about 50 MB from the app to no effect.

[dharmenbavaria]

Having the same issue, changes to one specific file fails to push everything with the same error mentioned in the main discussion, if you revert that file change it git push works, so there is definitely something going wrong.

[alexanderameye]

Exact same issue since recently +1

[mkjsix]

In our case, the workflow has been running for months without any issue and the last successful execution was last week on May 12th 2023. So, I think the problem can't be the content of our repository, which has not changed significantly over the last year, but definitely some recent modification of the execution environment of the GitHub actions.
Yesterday I also opened a ticket with Github support, but I have not received any feedback so far.

[Jason2866]

Same issue recently +1
workflow did run for month.

EDIT:
Adding this in my used forked action https://github.com/Jason2866/copy_file_to_another_repo_action/tree/http408_fix

git config --global http.version HTTP/1.1
git config --global http.postBuffer 157286400

like @jeanjerome did worked. Solved. Thx! (git lfs is already installed)

[aminvakil]

Is github going to be this way or is this a bug? Is there an official response regarding this mater?

[mkjsix]

@aminvakil I opened a ticket and GitHub support suggested having a look at helaili/jekyll-action#143, because this issue is related to a third-party action that it's not officially supported.

So, the solution to fix the helaili/jekyll-action@v2 seems to be what has been already suggested above. In my case, it works if I add the pre_build_commands:

    - uses:  helaili/jekyll-action@v2
      with:
        pre_build_commands: git config --global http.version HTTP/1.1; apk fetch git-lfs;
        token: ${{ secrets.GITHUB_TOKEN }}
        target_branch: 'gh-pages'

[aminvakil]

I'm not using helaili/jekyll-action@v2.
https://github.com/aminvakil/aur/actions/runs/5029785702/jobs/9021743297#step:11:177
It's basically doing git clone https://github.com/ansible/ansible in GHA.

[d-otis]

Thank you @mkjsix for specifying where to place the git config change.
Works like a charm! 🤩 🙏🏻 👏🏻

[julian-poidevin]

To answer @aminvakil : should an issue be opened on GitHub ? I doubt this discussion will have enough visibility.

[aminvakil]

@julian-poidevin I don't know how github works, whether they prioritize an issue or a discussion or something else.

As this discussion is already in home page of https://support.github.com/features/actions on "Helpful community posts", I'm not sure how to drag attention of someone from github here to this problem.

All I'm saying is if I had a list of issues to take care of (as a person, team, organization, etc.) I would focus more on issues that don't have a "Accepted answer".

I may be totally wrong and something else is going on in github though.

[MarkParker5]

Same issue since recently, waiting for an official response.

[aminvakil]

I just got this error on my system as well, seems it's not related just to GHA.

$ git --version
git version 2.40.1

[CometVoid]

I made a brand new repo specifically to try avoid this frustrating bug that seemingly is only effecting some repos. Github let me make 1 commit, but no more after that.

I just want to backup my notes man, but 'git push' no worky ;-;

[dobbelina]

Thanks for the fix @Jason2866
I have incorporated it into my own fork.

[Foxboron]

The same issue is preventing packages from being packaged on @archlinux.

strace git clone stalls at write(4, "0011command=fetch0014agent=git/2"..., 1443702) = 1443702 before getting the 408.

  -> Cloning moby git repo...
Cloning into bare repository '/home/foxboron/.cache/offload-build/tmp.6JYKszWSrz/moby'...
error: RPC failed; HTTP 408 curl 18 HTTP/2 stream 7 was reset
fatal: expected 'packfile'

No update from the Github team on this?

[julian-poidevin]

I really think you should be opening an issue if you want this to get resolved.
This discussion has been marked "Resolved" by the original author so I don't think GitHub will look at it 🫤.

[dobbelina]

I really think you should be opening an issue if you want this to get resolved. This discussion has been marker "Resolved" by the original author so I don't think GitHub will look at it 🫤.

Good point.
@jeanjerome should remove the "Answered" label as the given information is not a fix but a workaround.

[jeanjerome]

Alright guys, I'm removing the "resolved" label and let's see if it unlocks the situation.

[tpkessler]

The testing repository of Arch Linux contains an updated curl-8.1.1-2 that includes curl/curl@5c58cb0. This fixes the problem for me.

[jeanjerome]

Good catch @tpkessler

• This could be an issue with cURL, which in version 8.1.0 introduced support for HTTP/2 ( search CURLPROXY_HTTPS2: for HTTPS proxy that may speak HTTP/2), and version 8.1.1 fixed an issue with uploads (in http2: upload improvements).
• Additionally, the release date of version 8.1.0 aligns with the occurrence of the bug: May 17, 2023.

To be tested as soon as possible...

[aminvakil]

My issue has been resolved too with curl 8.1.1.

[jeanjerome]

Yes, it's working well now! Thanks.

[d-otis]

Working for me as well. TY for posting the answer! 🙏🏻

[langroodi]

From yesterday the issue is disappeared from my GitHub action and now it is working as normal. Are you experiencing also the normal situation again or the git on the GitHub runners works occasionally (sometimes good and sometimes bad)?

[dobbelina]

I assume this means we can remove the below fix work-around then?

git config --global http.version HTTP/1.1
git config --global http.postBuffer 157286400

[jeanjerome]

@dobbelina Yes, there is no longer a need for it

[cmxl]

I still had to set the http version to 1.1 although using curl 8.1.2 on Windows 10.
Git version 2.41.0 for Windows.
But i had to push changes to Azure DevOps.
Is there someone else with this problem?

[julian-poidevin]

The issue just re-surfaced for me, it was fixed before.