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

Miro Knejp May 23, 2017

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

0 votes
Edwin Kyalangalilwa Community Leader Aug 20, 2017

Try a regular

git clone --branch=foo

It will download the repo first then download the binary files 

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

3,376 views 3 22
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