News for hackers. Stuff that matters.

lindsayolson

Hey all - GitLab's 13.3 release is live today. Quick preview of what is inside:

Coverage guided fuzz testing: You can now run coverage-guided fuzz tests against your Go and C/C++ apps!

Kubernetes Pod health dashboard: In GitLab 13.3, you can view the health of your Kubernetes pods in the new out-of-the-box Pod health metrics dashboard (personal commentary: super excited about this one!)

Merge Request Approvals shows who participated in the review: Code review often involves multiple people and multiple iterations. It can be hard to know who has been reviewing the merge request, and which of those reviewers has approved and who hasn’t.

There is much more included in this release, so head over to our blog post (linked: https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-rel...) and check it out.

As always, let me, and our Product Team know what questions you have! (link to feedback issue: https://gitlab.com/gitlab-org/gitlab/-/issues/239761) -LO

Re:Tell HN: Locked out of Gitlab and lost years of work on Tuesday July 21, 2020 @11:28AM (#23907571)
Hey there - it's Lindsay from GitLab again. You and I connected on Twitter about this very thing.

I wanted to respond because I feel just terrible that you have had such a frustrating experience. :(

You are not wrong when you use words like "snafu" and "broken". If it's any consolation, you are not alone. Unfortunately, GitLab's messaging about this inconvenience got lost for more users than we anticipated. You are a victim of that and I want to let you know: we learned A LOT from this experience over on our side.

Ok, so what do we do about your account? If I am understanding correctly, your secondary email was verified, but your primary email is still NOT verified.

I can confirm that Support just now sent you another verification email that is unlikely to get lost in the mix this time. Please look out for it in your inbox in order to rectify this ASAP.

Again, I hope hope hope that we can regain some of the trust that was lost during this negative experience. Please keep me posted on when you get access again! Twitter: @communitylinds

Re:Accessing Gitlab Returns 403 on Tuesday May 19, 2020 @04:21PM (#23239698)
Git operations have been executing normally and we've verified the issue is resolved! https://gitlab.com/gitlab-com/gl-infra/production/-/issues/2... (status.gitlab.com)

Please don't hesitate to reach out to us with questions or concerns.

Lindsay GitLab Community Advocate

Hi! GitLab Community Advocate here: I noticed the issue you linked is closed. I believe the conversation is continued here: https://gitlab.com/gitlab-org/gitlab/-/issues/213080

Hope that is helpful. If so, feel free to add a comment so the team can see.