Microsoft just killed GitHub

status.github.com/messages?2018-10-22

OH NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO

Attached: Screenshot from 2018-10-22 15-35-14.png (1290x1722, 225K)

Other urls found in this thread:

encyclopediadramatica.rs/Girl_on_the_Internet_Syndrome
encyclopediadramatica.rs/Incel
archive.is/qRO8D
twitter.com/SFWRedditVideos

I think you are retarded

I think you need to poo in the loo.

>Trusting microshaft in the first place

>using github in the first place

>microshart

Ah there it goes. Extinguish

We didn't even get to the Embrace and Extend steps yet, Microsoft's getting efficient, time to invest.

This is what you get for not using cgit
>muh social coding

github microshafted by wangblows, what a surprise

Attached: 1514606268578.jpg (125x125, 3K)

What the fuck are you people on about? I downloaded a bunch of projects about ten minutes ago. It’s up.

>We are continuing to work to migrate a data storage system in order to restore access to GitHub.com.
>We're continuing to work on migrating a data storage system in order to restore access to GitHub.com.
>We continue to work to migrate a data storage system in order to restore access to GitHub.com.
>We continue to work on migrating a data storage system in order to restore access to GitHub.com.
>We continue to migrate a data storage system in order to restore full access to GitHub.com.

Why did they use 5 slightly different ways to say the exact same thing?

to look busy so they get more bonus

works on my machine

It looks like they have to provide an update every thirty minutes.

Looks like microsoft still can't fix this

Attached: Screenshot_2018-10-22 October 21 Incident Report.png (1368x1038, 150K)

They get copied to twitter, which does not allow duplicates.

Ah, the migration has already begun. Already the same quality as their other services.

> MySQL databases
Dumb Microsoft.

We've had databases as long as we've had computers. Why isn't this a solved problem?

Attached: 1539404296632.jpg (800x680, 330K)

>goyhub
|>
|3

Databases are pretty easy to break and hard to restore. It's too much hardware and software to ever become truly reliable.

have you ever tried managing a data base?

Did they change the servers over to Windows Server?

encyclopediadramatica.rs/Girl_on_the_Internet_Syndrome

encyclopediadramatica.rs/Incel

Attached: IncelInside.jpg (1000x1000, 76K)

dubdubs confirm

>cant do work because all of our code is on a private github repo

fucking kek, free day off of work at this rate

>not being on gitlab
wew lad

OOPS! We accidentally the database and filesystem that saves 80% of open source projects, LOL, SORRY!
Embrace, Extend, Extinguish.

Nice try but I ported all my shit to gitlab months ago.

this is some next level faggotry

archive.is/qRO8D

lrn2archive

HOW CAN THIS HAPPEN

WE REPLACED ALL OUR DEVELOPERS WITH TRANNIES

IT SHOULD BE RUNNING SMOOTHER THAN EVER

Attached: 1533038350767.png (512x512, 125K)

eat shit and die with your botnet site

Post tits

gib back my repo

Attached: m$.jpg (1101x651, 56K)

...

sad_pepe.jpg

kys dumb frogposter

works on my machine

CATASTROPHIC

DATA

FAILURE

*dumb github user*

if only we had hired a more diverse IT team this never would've happened

Attached: 1520556796429.jpg (821x831, 138K)

Github does not work in your machine, you retarded mouth breather

Why do they use Microsoft?

Literally who cares

Just pointing out that msft hasnt actually bought github yet

If only your company had used a Distributed Version Control System.

>Fuck partition tolerance, that shit never happens
>It happens
Solid kek. The CAP theorem holds true. You can have 2/3 of consistency, availability, and partition tolerance. GitHub chose consistency and availability. So when a network partition happened, they ended up with two databases thinking they were the master. Partition gets solved and now you have two databases which conflict, because through the partition people were writing to it. Your database is no longer consistent.

Never choose CA. CP and AP are the only real options (your data is only eventually consistent, or your writes fail during a partition.) Picking CA is awesome until eventually it fails catastrophically because networks fail.

>HE thinks CAP is always 1-1-0
bwahahahahahahahahahahah

You should always go 100% into P and then your trade-off is how quickly you want consistency. I never said it's a binary choice though, only that you can only have 2/3.

I bet a diversity hire did this.
Should have kept the meritocracy going that made them strong.

Welcome to the experience of using Microsoft developer services.
My company fell for the Azure, VSTS (Now Azure Devops), AppCenter meme and they had serious outages last month (or was it the month before?), too.

Microsoft is incredibly incompetent when it comes to their online services. It's frankly quite ridiculous.
Must be due to their insistance to use Windows Server with MSSQL instead of Loonix, since it's free for them
.