Tom Elliott

@bstaples Not gonna lie, it's tempting.

Tired of the pain yet? Come to GitLab and take back control of your destiny. I’ll even throw in the first year free for anyone switching from GitHub who signs a new three year agreement. DM me

This is way broader than the pull requests page being empty. We're seeing dropped webhook calls and re-runs of failed checks not being associated with the original PR. They've started mentioning elasticsearch, so could be that anything listing PRs internally is also failing.

The hits just keep on coming with GitHub...

After Thursday's GitHub incident, I got thinking about SLOs. Most reliability discussion is limited to uptime and latency, but there are so many more things to pay attention to. I wrote a post about correctness SLOs and why their bar is 7 nines or more! telliott.me/posts/pipeline…

@neerajjj6785 I'm not sure it exists 😅 Unless we count projects with a very small number of users.

@theotherelliott What's your pick?

Now hold on a second...

I'm generally ok with AI chat interfaces, but there's something about replacing a phone tree with an AI voice assistant that just seems...wrong. On the plus side, it immediately understood "I want to talk to a human". Call centers aren't going away.

@eatonphil Glad to hear it was a good event! Sorry I couldn’t make it in the end.

BugBash brought quite the crowd

@paulgb “Head Hunter” on the other hand is title inflation.

“headhunter” is such a violent way to say you work in HR

@ashoKumar89 I’d accept it until it broke something I cared about. Then I’d read the HTTP spec again.

A user deletes a resource. Your API returns 200. 
But the deletion is async and not completed yet. 
The resource may still appear for a while. Is this acceptable or a bad API contract?

@kdaigle Appreciate the follow up here (and the list via email we could use to check our fixes). Out of interest, is the 4M merged number the total number of merges across all users, or just those using merge queues with squash/rebase?

Wanted to provide more clarity about this. Yesterday, we had a regression in merge queue behavior where, in some cases, squash or rebase commits were generated from the wrong base state, making earlier changes appear reverted in branch history. 2,804 pull requests out of over 4M merged on April 23 (roughly 0.07%) were affected. We fixed the issue, we've contacted every impacted customer, and we're expanding our automated test coverage for merge queue operations. The team will be updating the status page with RCA details as well.

@GregKara6 That's pretty much exactly the sentiment we had in the office when we saw the post.

WAIT SO I WASNT GOING CRAZY IS THIS WHY I REMEMBER I DID SOMETHING BUT IT ISNT THERE

@QixOfMTF This is definitely one of the places where people forget how much GitHub layered on top of Git, but still expect the same guarantees. We've probably been too trusting.

@theotherelliott "with Git" People still confuse GitHub with Git, it would be great if they go down actually

This GitHub incident is insane. Merge queue commits have been reverting previously merged commits at random. This not only breaks the mental contract teams have with Git in general, but is subtle enough to be really hard to unravel after the fact. githubstatus.com/incidents/zsg1…

@vnicolici @JedFrankowski The “everything’s OK” alarm.

@JedFrankowski @theotherelliott I received 25 incident notifications from GitHub in the last 24 hours. It would probably be more efficient at this point to notify me only when there are no incidents.

@depthfirstsearc We didn’t see it until after the fact either, when it was buried in the history.

@theotherelliott Weird, I don’t see this in the status

@davidxia_ Good think we already did our own audit, right? 😅 I think the postmortem will provide some good popcorn reading!

@theotherelliott I'm looking forward to their post-mortem. They emailed us with a list of affected commits. For very active repos, this is a major headache. 😭

I recently hit the two month mark at @modal and I’d love you to come join me! Hard to believe it’s been 8 weeks, we’re shipping so often, learning fast, and growing even faster. Plenty of brand-new, empty desks and interesting technical challenges. #careers" target="_blank" rel="nofollow noopener">modal.com/company#careers

You might have heard of merge queues. You might even have used one at work. If so, you might even hate them. But if you've never used them before, how do you decide if your engineering team would benefit from a merge queue? telliott.me/posts/why-merg…

A teachable moment from AI