[woodcut]

Side topic here: Anyone noticed how bad Git-LFS is?

We've been using it in production for dataset versioning and noticed that it's not even at a beta stage, perhaps pre-alpha. It gets corrupted by it's own volition at random, working seamlessly for a day then suddenly 'git clone' will fail repeatedly, until the repository is rolled back, or it magically fixes itself.

I don't understand how it got integrated into Github, and now i see sourcetree and other clients support it. gah.

[Camillo]

Git-LFS was developed by Github, presumably so they could expand their business to manage more types of content.

[woodcut]

I mean i understand that, but they didn't seem to do much of an evaluation before launching.

[thatguysteve]

Curious about the git clone failures, did you have to fix errors on the client side, or update the repo to get it to work again?

[woodcut]

Most of the time it'll say "TLS handshake timeout" in the logs, so I just wait for githubs amazon instances to come back online. Other times its something I committed that others can't pull, so I'll revert then re-commit. A divining stick is recommended.