Re: GitLab status

2020-06-22 Thread Ben Gamari
Ryan Scott writes: > Just as an FYI, there appears to be some data loss from this migration. For > example, I pushed a commit to !3536 [1] that appears to have been dropped, > leading to confusion here [2]. To make things worse, I never received an > e-mail notification for this comment—I only di

Re: GitLab status

2020-06-22 Thread Ryan Scott
Just as an FYI, there appears to be some data loss from this migration. For example, I pushed a commit to !3536 [1] that appears to have been dropped, leading to confusion here [2]. To make things worse, I never received an e-mail notification for this comment—I only discovered it by chance. I als

Re: GitLab status

2020-06-21 Thread Ben Gamari
Ben Gamari writes: > Ben Gamari writes: > >> Hi everyone, >> >> As you may have noticed, yesterday was marked by rather consistent CI >> failures. I believe I have now fixed the root cause but do let me know >> if you see any further issues. >> >> Below I have included a brief post-mortem descri

Re: GitLab status

2020-06-20 Thread Ben Gamari
Ben Gamari writes: > Hi everyone, > > As you may have noticed, yesterday was marked by rather consistent CI > failures. I believe I have now fixed the root cause but do let me know > if you see any further issues. > > Below I have included a brief post-mortem describing the incident and > what we

GitLab status

2020-06-20 Thread Ben Gamari
Hi everyone, As you may have noticed, yesterday was marked by rather consistent CI failures. I believe I have now fixed the root cause but do let me know if you see any further issues. Below I have included a brief post-mortem describing the incident and what we plan to do to prevent it recurring