Failed Git Push exits silently

Xevion commented 2 years ago

This job instance that failed to push for me.

The job exited with an overall success.
The remote dropped the connection when it was pushed.
The failure exit code was not picked up by helaili/jekyll-action@v2.

I'm not 100% sure about WHY it failed, but this article specifies it is common with excessively large commits.

I believe my site (at the time) weighed somewhere above 100MB. After removing assets and re-building, the gh-pages branch commit in the action was successful (example).

Stwissel commented 1 year ago

Same problem here. The push failed with a 408 which wasn't picked up. Our site is comparable tiny (< 10 pages. Delete & rebuild gh-pages didn't help.

From the log:

Publishing to beyonddemise/beyonddemise.github.io on branch gh-pages
[main (root-commit) 0852bf2] jekyll build from Action f1a92ef7df1fcadcd5d3455d56a5eb2e52fd940a
 14 files changed, 11530 insertions(+)
 create mode 100644 .nojekyll
 create mode 100644 CNAME
 create mode 100644 LICENSE
 create mode 100644 README.md
 create mode 100644 assets/favicon.ico
 create mode 100644 assets/img/bg-mobile-fallback.png
 create mode 100644 assets/mp4/bg.mp4
 create mode 100644 css/main.css
 create mode 100644 css/mobile.css
 create mode 100644 css/reset.css
 create mode 100644 css/styles.css
 create mode 100644 index.html
 create mode 100644 js/scripts.js
 create mode 100644 site.webmanifest
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

EverettBerry commented 1 year ago

Same problem here. Repo is about 100 MB. Going to try to move some items out.

ryan-p-randall commented 1 year ago

I'm also getting the same HTTP 408 error.

When I dig into the commit history, I see this annotation:

Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/cache@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Maybe it's not the size of the repo, but the action itself needs to be updated to node 16?

EverettBerry commented 1 year ago

I tried this upgrade and it did not help.