Skip to content
Russell Keane
Main Navigation HomePosts

Appearance

Sidebar Navigation

2025

February (1)

Dynamically setting prev and next links in Vitepress

2019

November (1)

CloudFormation template failing to deploy

2018

March (1)

Subst'ing a drive in Windows 7 / 10

January (1)

Groovy - unable to resolve class

2017

October (2)

Reordering pages in LIFERAY forms

Spring / ZUUL - Failed to introspect annotated methods

June (1)

Sourcetree stuck on POST (chunked)

March (1)

Turning off Windows 10 ads

2016

December (1)

Failure to install / update ruby gems

July (2)

PostgreSQL - Casting integer to interval

piggly trace- invalid multibyte escape

June (1)

Jenkins stuck on "Retrieving Git references..."

March (1)

Jenkins & Groovy - accessing build parameters

2015

November (2)

Creating a Jenkins slave as a Windows service

Why Jenkins?

On this page

The problem ​

When pushing large files up to BitBucket (git in general?) Sourcetree gets stuck on the POST command stating:

shell
    POST git-receive-pack (chunked)

It seems to be that Sourcetree's (or possibly just git's) ability to "chunk" files and send them is broken.

Note: the exception / error message (1) in the following image is nothing to do with the chunking issue and does not seem to affect pushes in any way; it is simply highlighted here to tell you to ignore it for the purposes of this article.

Here you can see the chunked message (2) in the Sourcetree window:

chunked

The solution ​

This is quite a simple one.

Open a git bash window. I tend to use one in the folder of the repo I'm working on by right clicking in the explorer window and choosing "Git Bash" (3)

git_bash

Now type the following (4) in the git bash window then hit return:

shell
    git config http.postBuffer 1000000000

git_bash2

The number can be pretty much anything as long as it's larger than the size (in bytes) of the thing you're trying to push. I'm sure there will be some reason why it should be multiples of 1024 or 8k or something of the like but, hey, it works. If you have a better explanation of what this number should be, please leave a comment or get in touch.

You should now re-push your branch to the remote (even if sourcetree isn't highlighting the need to push) and all will be good in the world.

Pager
Previous pageTurning off Windows 10 ads
Next pageSpring / ZUUL - Failed to introspect annotated methods

All views expressed are my own

Copyright © 2015-present Russell Keane