I feel like HN could just have a traffic monitor that adds a little icon to the main page. Like "I dunno what's up, but there's a LOT of y'all here right now, so something probably is".
GitHub issue - resolved
41–50 of 169 posts
Re: GitHub issue - resolved
#42[deleted]
Re: GitHub issue - resolved
#43Suppose you start your day by downloading some code from GitHub to work on. This morning you would be stuck. Do you save code on your hard drive or company servers or GitLab to handle this risk?
Re: GitHub issue - resolved
#44Ever since Microsoft took over...
...Github has gotten significantly better.
...and Github is down...
Re: GitHub issue - resolved
#45HN should really have a “Down HN” category, as this is the most reliable place to get this information.
I find downdetector to be quite reliable. You can pick up on a spike of reports very quickly.
HN though comes with all the commentary.
Re: GitHub issue - resolved
#46Why 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 find this strange too. GH seems to have more major incidents lately...
Re: GitHub issue - resolved
#47Re: GitHub issue - resolved
#48Why 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.
Re: GitHub issue - resolved
#49Earlier quoted context omitted.
How sure are you that none of those commands has a dependency on GitHub infrastructure?
Because I use Github only for git hosting and actions (building & deploying containers). In this case, code is already in my computer, and I can build and ssh to server and pull&run the new container. "docker buildx build ... -push" "ssh ...@..." "docker pull ..." "docker compose up ..."
That assumes that none of your Docker images have a build step that includes interacting with GitHub, or if some do, that you have every affected layer already cached on your local computer.
Re: GitHub issue - resolved
#50Earlier quoted context omitted.
I like to reduce the single point of failure count in my projects as much as I can, with common sense. My backup system is running a few cli commands instead of git push, so it's a no brainer. YMMV.
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.