GitHub Service Outage (github.com)

← Back to Stories (view on slashdot.org)

GitHub Service Outage (github.com)

Posted by whipslash on Wednesday January 27, 2016 @02:13PM from the technical-difficulties dept.

New submitter thebigjeff writes: Beginning at around 7:30pm EST on 1/27/2016, GitHub's core services have been offline. Most repositories and other functionality is inaccessible. The status page is calling it a "significant network disruption." More from The Register: GitHub falls offline, devs worldwide declare today a snow day.

6 of 117 comments (clear)

Min score:

Reason:

Sort:

"7:30 PM" by Anonymous Coward · 2016-01-27 14:21 · Score: 1, Insightful

So is that Ulaan Bataar Standard Time, or what?
This is almost as bad as the suits in California thinking that *of course* all its employees in Europe and Asia use PST. Gawdz.
Decentralized source control by manu0601 · 2016-01-27 14:51 · Score: 4, Insightful

The selling point of git was to be a decentralized source control system.
It is interesting to see people telling about a snow day while they have a tool that do not require a central repository
1. Re:Decentralized source control by sunderland56 · 2016-01-27 15:00 · Score: 4, Insightful
  
  Even if you are using a source control system that *does* require a central repository to be up: since when did the inability to check in prevent you from writing and debugging code? If interacting with git/svn/clearcase/etc. is more than 0.1% of your work day, maybe you're not doing it right.
  If source control being inaccessible means you get the day off.... let's just say that ClearCase users would be extremely happy.
2. Re:Decentralized source control by sunderland56 · 2016-01-27 15:54 · Score: 5, Insightful
  
  So: no incoming bugs or feature requests, no merging other people's code, nobody pinging you every 5 minutes? Around here that's called "a day where I can be productive".
3. Re:Decentralized source control by Dutch+Gun · 2016-01-27 18:46 · Score: 3, Insightful
  
  I know it's fun to be snarky about the fallibility of the cloud at times like these, but in fairness, I think one has to measure these unexpected outages against the productivity gains of having a convenient centralized point to synchronize your project online, especially for historically decentralized teams like your typical open source projects.
  The notion that "git is decentralized" is obviously tempered against the requirement to synchronize everyone's repositories, right? Still, I agree... the whole "github is down, I can't code today" is an even weaker excuse than something like "it's okay if I'm goofing off - I'm compiling." One of the benefits of git (and Mercurial as well, which is actually my system of choice) is that it's trivial to make a local branch and start working on some new feature. If you're working on a project, then by definition you have an entire copy of the repository locally - it's not like you need to connect to github just to see your code or check in changes locally. Even if you can't see your bug/todo list, that just means it's a great time to make a branch and start some other little project, like doing some refactoring or code cleanup - or even, heaven forbid, some documentation.
  
  --
  Irony: Agile development has too much intertia to be abandoned now.
4. Re: Decentralized source control by prefec2 · 2016-01-27 20:22 · Score: 3, Insightful
  
  There are also decentralized ticket systems. Even though you should know enough about your tickets and tasks to have something to do for one day ;-) And if all fails, update the documentation.