It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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 https://bitbucket.org/user/repo.git/info/lfs/objects/batch: read tcp 1.2.3.4:1051->5.6.7.8:443: i/o timeout

We're cloning the repository with

git lfs clone --branch=foo https://bitbucket.org/user/repo

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

0 votes
edwin Community Leader Aug 20, 2017

Try a regular

git clone --branch=foo https://bitbucket.org/user/repo

It will download the repo first then download the binary files 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Atlassian supported Jenkins integration for Bitbucket Server

We’ve been building a plugin to integrate Bitbucket Server and Jenkins CI, and I’m excited to announce that our alpha is ready to download and install. It lets you seamlessly configure a Jenkins job ...

1,087 views 3 17
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you