Slashdot Mirror
GitHub's Website Remains Broken After a Data Storage System Failed Earlier Today (theregister.co.uk)
Github engineers are trying to repair the data storage system underpinning the code hosting website, which has been presenting users with a "What!?" error for much of the Sunday. From a report: Depending on where you are, you may have been working on some Sunday evening programming, or getting up to speed with work on a Monday morning, using resources on GitHub.com -- and possibly failing miserably as a result of the outage. From about 4pm US West Coast time on Sunday, the website has been stuttering and spluttering. Specifically, the site is still up and serving pages -- it's just intermittently serving out-of-date files, and ignoring submitted Gists, bug reports, and posts. Sometimes, it appears to be serving a read-only cache or older backup of itself, although some fresh code pushes are coming through onto the site. From the status page, it appears a data storage system died, forcing the platform's engineers to move the dot-com's files over to another box. In the meantime, some older versions of files and repos are being served to visitors and users. "We're continuing to work on migrating a data storage system in order to restore access to GitHub.com," the team said just after 5pm PT, adding in the past few minutes: "We are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process."
INb4 "Microsoft Broke It!" - they've yet to actually take over. They're still waiting on government approval of the acquisition.
just signed the GitHub purchase.
Slashdot, fix the reply notifications... You won't get away with it...
"All ops staff required to use pure HoloLens interface with floating console and keyboard!"
*Github immediately convulses*
"There is more worth loving than we have strength to love." - Brian Jay Stanley
If you'd been using SourceForge instead, you wouldn't have to deal with the outage.
This Slashvertisement brought to you by SlashdotMedia(TM).
Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
What is there storage back end? and what VM system? are they useing?
Does anyone remember back when they trashed most of the cloud data of Sidekick smartphone users shortly after they acquired the company? This was even covered by Slashdot!
https://hardware.slashdot.org/...
Looks like a repeat of the bumbling.
you may have been working on some Sunday evening programming, or getting up to speed with work on a Monday morning, using resources on GitHub.com -- and possibly failing miserably as a result of the outage
if not being able to make posts and gists breaks your workflow to the point of "failing miserably"...then you are just a miserable failure :-)
Which data storage sytem would that be? Brand and model. I want to know so that I can think badly of it, or possibly of the persons who configured it, but most probably the vendor.
When all you have is a hammer, every problem starts to look like a thumb.
A possible clue:
Moving to bare metal and federated storage on Rackspace has brought our average Rails response time to consistently under 100ms
But that post is ancient.
When all you have is a hammer, every problem starts to look like a thumb.
It's
the
whole
Hotmail
Debacle
all :-D
over
again.
Another possible clue:
I’m a developer on Openstack’s object storage system, and I believe that Openstack is uniquely positioned to achieve this vision.
In contrast, I believe that Openstack is a steaming pile of impenetrable Python poo, especially its storage architecture. If this is indeed their platform then I am not at all surprised to hear that Github admins are now busy failing their files over manually.
When all you have is a hammer, every problem starts to look like a thumb.
NodeJS is an event driven not blocking io server that can be used to build high performance applications. Everyone knows that Python uses blocking IO. Python was developed before async was discovered.
sarcasm
Microsoft would just run CHKDSK to fix it.
I'm tellin' you people... these contraptions aren't really prime time
Thanks Microsoft.
Breaking shit and blowing stuff up...
Chas - The one, the only.
THANK GOD!!!
They just need to figure out which one of his twenty five personalities Chris is pretending to be right now! But the nice thing is the storage closets at Github will be clean after. And all the fridges in the break room too!
(Just don't go near Chris when you hear those awful slurping and gnashing sounds!)
Yeah, Microsoft has this. Everything it touches turns into shit.
Isn't that what Microsoft did to most acquisitions?
That thing does seem to delete files whenever it feels like.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
This is Github, it doesn't exactly run on a single server nor have a single point of failure. Rather it's called a Fire Drill in IT, and done by Sociopathic PHB managers. The gist of it is you create an outage forcing your target (say... a company you just aquired or a team) - to act. You drill the hell out of them to turn over documentation, training, etc. in the process.
It's NOT the same as cross training. They will use the outage(s) as weapons to implement some other changes which can be anything from changing who manages it to structural.
More outages, more weapons.
I'm curious. Are you just some bored IT guy who likes a laugh so post as AC, emails himself a reminder of stories trolled so you can come back later and read some lols?
Because they opened their recta to LGBT tapeworms.
Besides, it turns out that their "CoC" demands its own abolition. To begin with, the "CoC" itself doesn't escape its scope, for according to the same "CoC":
"**This Code of Conduct applies** both within project spaces and **in public spaces when an individual is representing the project or its community**. Examples of representing a project or community include **using an official project e-mail**, ..."
The "CoC", being spread in public spaces as, ostensibly, a "representation" of, among others, the Linux developer community, is subjected to itself. Indeed, said "representation" uses "an official project e-mail":
"Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by **contacting the Technical Advisory Board (TAB) at **."
As per the above statute, harassment is deemed not aligned to the "CoC", neither is any threat:
"**Maintainers have the right and responsibility to remove, edit, or reject** comments, commits, code, wiki edits, issues, and **other contributions that are not aligned to this Code of Conduct**, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, **threatening, offensive**, or harmful."
But it so happens that "Maintainers who do not follow or enforce the Code of Conduct in good faith **may face temporary or permanent repercussions** as determined by other members of the project’s leadership" is a blatant threat of harassment. Of course the "CoC" itself is a threat if it is a law at all.
Hence this "CoC" transgresses this "CoC". If it is not de jure destroyed by itself (the "CoC" compels the "maintainers" to permaban themselves, taking said "CoC" with them*) then it is weak, laxity obtains and nobody need pay attention to it, de facto destroying it, which is the better case, as nobody has hitherto pointed out this obvious loophole. On the other hand, this silence could betray a real blindness or "rigorous" discharge on the repressive apparatus' part (offensive and therefore *not rigorous* in avoiding offence against the CoC), either of which may reflect pretty badly on the Linux kernel's code quality, architecture, *merit*...
* They say "**Maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions** as determined by other members of the project’s leadership" (CoC) but then, since they don't *cut* their unCoC out (for reasons expounded in a previous post), they neither follow (on its way out) nor enforce it (by kicking said CoC in its unballs), they must, according to their CoC, "face temporary or permanent repercussions".
most likely situation, in my opinion. Another reason to leave GitHub and switch to GitLab.
Free Software world hero Linus Torvalds was forced to resign from the Linux kernel project by blackmail. He fell for a honeytrap and was threatened with a #MeToo purge if he didn't resign. It's a corporate power grab, using "Social Just-Us" as a tool.
Err!?
That's a god damn good idea! Will help all those boring days at work! Thank you kind sir for adding another troll to slashdot for the lulz.
The storage back-end is called The Cloud, and it stores The Bits. Fortunately, everything is backed up a million times in Git, so somebody has a copy.
Support my political activism on Patreon.
Git seem to be working for me. But travis isn't starting on the Pull requests.
Except for the github source code, which is in Subversion.
Remember, You are unique...just like everyone else.
It was only running on Subversion, but I it was perfect for a small team. And the revision discussion feature was awesome.