GitLab Database Incident – Live Report

Re:GitLab Database Incident – Live Report by sytse on Tuesday January 31, 2017 @08:19PM (#13537262)

Thanks, not feeling great about the job we're doing today, but we'll learn from this.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by antocv on Wednesday February 01, 2017 @05:44AM (#13539729)

The way you are open about this and do not blame the engineer who did "rm -Rvf" (he knows he fucked up, suffers enough already), and seeing that improvements can be made and you're willing to do them.

Applying for work with you now, and moving all my stuff to GitLab.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by mahnunchik on Wednesday February 01, 2017 @07:39AM (#13540228)

Move files to GitLab: git status & rm -Rvf .

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by sytse on Wednesday February 01, 2017 @06:27AM (#13539872)

Thanks for your interest in working at us.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by jdhendrickson on Tuesday January 31, 2017 @09:21PM (#13537620)

More than loving your service we like you guys as people and trust you to get things straightened out. I wouldn't host my code with anyone else despite this.

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by knocte on Wednesday February 01, 2017 @01:29AM (#13538765)

Losing 6 hours of data is not a big deal! Kudos!

[ Parent | on HN ]

Re:GitLab Database Incident – Live Report by sytse on Wednesday February 01, 2017 @06:27AM (#13539870)

It is a big deal to us. It should never be more than an hour and we should be able to recover much quicker. But thanks for the kudos.

[ Parent | on HN ]