Earlier quoted context omitted.
...Github has gotten significantly better.
...and Github is down... https://www.githubstatus.com/
...and out every single month to no end to the outages...
GitHub issue - resolved
51–60 of 169 posts
Re: GitHub issue - resolved
#52I cant push anymore! Anyone else ?
Re: GitHub issue - resolved
#53Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.
I truly doubt you are running at the scale of GitHub both in terms of users, complexity, and amount of data.
Re: GitHub issue - resolved
#54Yup. Tried pushing and got "remote: fatal error in commit_refs". Was trying to understand what I was doing wrong.
Same here haha. StackOverflow informed me that it means GitHub is down, and indeed it was.
I have to wonder if Git could somehow report this better. I guess it depends on exactly how GitHub is down, but "fatal error in commit_refs" made me worry that my local repo was somehow hosed.
Re: GitHub issue - resolved
#55HN should really have a “Down HN” category, as this is the most reliable place to get this information.
Everytime something has degraded performance or is down for me: 1. check my internet connection 2. check HN 3. check official statuspage
HN is de facto the fastest secondary source for any current event related to tech.
Re: GitHub issue - resolved
#56Why GitHub is down so often? Why is it not possible to keep it up 100% of time (without counting physical failure)?. I haven't seen any down time for my system (it has hundreds of thousands of users online) in months since I have completed the setup.
I'm sure your scale is similar.
Google search is basically never down.
AWS is basically never down.
WhatsApp is basically never down.
Time for GitHub to grow up?
Re: GitHub issue - resolved
#57Earlier quoted context omitted.
How sure are you that none of those commands has a dependency on GitHub infrastructure?
I understand the point you're making here, but I feel it is being made in an effort to prove hakanderyal technically wrong rather than to evaluate the practicality of single points of failure, which is what they're trying to promote. I this this conversation would be much more helpful and insightful if it was kept on that evaluation track rather than trying to have a final word.
I don't think "GitHub is down" threads are known for the quality of their conversation, but sure.
I also agree with reducing (increasing?) single points of failure. I'm not trying to be pedantic, but rather observing that in practice, it's not nearly as easy as spinning up a backup Git server (which is already hard enough).
Maintaining two classes of build infrastructure throughout all your dependencies is probably not a worthwhile problem to solve, unless you want to control for the improbable risk that GitHub will be down for weeks at a time. You'd be much better off ensuring that you are able to perform rollbacks without needing to pull from the external world, because this way the worst case scenario is you run a stale version for the time that GitHub is down, in the off chance you pushed a broken version right before the outage.
Re: GitHub issue - resolved
#58https://www.githubstatus.com/incidents/52z0j6phhnjs
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
For what it's worth, it's powered by statuspage.io, which is relatively industry standard for status pages.
Re: GitHub issue - resolved
#59https://www.githubstatus.com/incidents/52z0j6phhnjs
Seems better done than a lot of status pages, runs on separate infra, updated, has a way to subscribe, etc. However, saying "degraded performance" when you know it's "down for everyone" is an industry phrasing thing that's irritating. AWS also has "elevated response times" when everyone is seeing 5xx errors, or infinite response times.
It's not down for everyone. I can browse just fine, but my pushes get rejected, so that qualifies as "degraded performance" for me.