jeffreytse / jekyll-deploy-action

🪂 A Github Action to deploy the Jekyll site conveniently for GitHub Pages.
MIT License
339 stars 44 forks source link

Increase git post buffer size #80

Closed ambersun1234 closed 6 months ago

ambersun1234 commented 6 months ago

Description

I've run into the following error in the build

error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

According to git config documentation

Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests.


You can check the error at https://github.com/ambersun1234/ambersun1234.github.io/actions/runs/8483339855/job/23244517355

Fix

This PR adjust the git post buffer size to 524288000

Tahanima commented 6 months ago

@jeffreytse, can you please look into this? I've experienced the same issue this PR is trying to address.

Qumatah commented 6 months ago

I ran into this issue too! Can confirm that this fixes it!

TimothyWeng commented 6 months ago

Running into the same issue, is there any way to fix it before merging?

ambersun1234 commented 6 months ago

@TimothyWeng You can use my fork ambersun1234/jekyll-deploy-action@52f40044bb2a2b5d7365472ed640bfd412689d41

luz-ojeda commented 6 months ago

Is anyone still having similar problems? I'm getting

error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

But I'm not sure if it is related to OP's problem

jeffreytse commented 6 months ago

Hi, I recommend to use the ssh approach instead of http approach to avoid the issue, please refer to FAQ.

ambersun1234 commented 6 months ago

Hi @jeffreytse

Thanks for sharing the ssh approach, it indeed resolve the issue I'm facing right now

However I personally would prefer using http approach instead of ssh, because it simplfy the configuration that ssh needed Increase git post buffer size can ensure both ssh and http works without issue