Cloning LFS sometimes fails with read tcp i/o timeout

For about a week or so we have sporadic failures on our SppVeyor server when cloning our repository. When it happens the message is always the same

batch response: Post read tcp> i/o timeout

We're cloning the repository with

git lfs clone --branch=foo

The version of git on AppVeyor is currently 2.13.0(2) and git lfs is 2.1.0

Is there anything that can be done to check whether this is a problem on Bitbucket or AppVeyor? It only started occurring about 5 days ago and since then it breaks our builds multiple times a day because checked out binary files end up corrupted. I couldn't find a way to run something like an LFS integrity check on the bitbucket interface.

1 answer

Try a regular

git clone --branch=foo

It will download the repo first then download the binary files 

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

638 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot