im getting a 500 (from NYC) on the main page + i cant push to remote repos
Checked from India, everything seems to be down...
Github major service outage
11–20 of 82 posts
Re: Github major service outage
#12I find it somewhat odd that, given git's emphasis on distributed version control, we see so many git users have centralized themselves quite heavily on GitHub.
Whenever GitHub runs into problems like this, it reminds me of when a team's CVS or Subversion servers used to go down. It could be a pretty disruptive occurrence, if it wasn't resolved quickly. While git can theoretically handle this better, in practice the use of GitHub, for instance, renders git just as susceptible.
Re: Github major service outage
#13Database outage causing everything to go down?
Re: Github major service outage
#14Least reliable service that I pay for by a long shot.
Re: Github major service outage
#15I find it somewhat odd that, given git's emphasis on distributed version control, we see so many git users have centralized themselves quite heavily on GitHub. Whenever GitHub runs into problems like this, it reminds me of when a team's CVS or Subversion servers used to go down. It could be a pretty disruptive occurrence, if it wasn't resolved quickly. While git can theoretically handle this better, in practice the u…
Thats not true, with CVS/SVN you can not commit, log or do anything while the server is down.
With git you can still commit to your local tree, push it to another server or send patches.
While it might slow down workflows using github.com for push/pull its not that complicated to temporarily push/pull via another server.
Re: Github major service outage
#16Why Unicorn Why!
So, what's better than Unicorn ?
Re: Github major service outage
#17I find it somewhat odd that, given git's emphasis on distributed version control, we see so many git users have centralized themselves quite heavily on GitHub. Whenever GitHub runs into problems like this, it reminds me of when a team's CVS or Subversion servers used to go down. It could be a pretty disruptive occurrence, if it wasn't resolved quickly. While git can theoretically handle this better, in practice the u…
How is it at all odd? Github offers a convenient platform for using git. People use it.
If Github were to explode forever tomorrow, active projects would just take their locally cloned repositories, and put them online somewhere else and carry on committing (albeit sans github's awesome social tools). That's the real power git offers us.
It's just a fact of reality that most projects centrally organize through a few bottlenecks. It's easier for people to remember where to go, if there's only one place to go to. But if you're really concerned about it, i suppose you could build a tool to automatically sync a github repo w/ another 3rd party host if you wanted (or visaversa).
Re: Github major service outage
#18Least reliable service that I pay for by a long shot.
Must not pay for very many services? https://status.github.com/graphs/past_month
Re: Github major service outage
#19The status page says that "Code Downloads" is "Normal". How do you get to the downloads page for a given repo? Is there some canonical form for a URL for repos? Maybe while they're fixing it we can still download code...
try: git://github.com/{user}/{repo}.git or https://github.com/{user}/{repo}.git anyway, not working right now for me (Italy) EDIT: working, give it 30 seconds to start.
Nope, no joy - 30 seconds or otherwise.
Re: Github major service outage
#20I find it somewhat odd that, given git's emphasis on distributed version control, we see so many git users have centralized themselves quite heavily on GitHub. Whenever GitHub runs into problems like this, it reminds me of when a team's CVS or Subversion servers used to go down. It could be a pretty disruptive occurrence, if it wasn't resolved quickly. While git can theoretically handle this better, in practice the u…
How is it at all odd? Github offers a convenient platform for using git. People use it. If Github were to explode forever tomorrow, active projects would just take their locally cloned repositories, and put them online somewhere else and carry on committing (albeit sans github's awesome social tools). That's the real power git offers us. It's just a fact of reality that most projects centrally organize through a few…
Yes, but Github is not just about Git hosting, it's about all those awesome social tools. If you use Issues as the main bug tracker, for example, you've got a problem.