[deleted]
GitHub was down
221–230 of 288 posts
Re: GitHub was down
#222RIP to all those who host their websites on GitHub pages :(
I checked, and my pages-based site was down, but it is back up now.
Re: GitHub was down
#223Earlier quoted context omitted.
delaying SLA
This is at least a multi-million dollar payout (if they admit to it). All GitHub Pages say > We're having a really bad day. > The Unicorns have taken over. We're doing our best to get them under control and get GitHub back up and running.
At the moment, all github services seem to be restored, and the github status indicates that the problem is still ongoing. I don't think it's related to the SLA, but rather to the monitoring, which is not live. There are a few minutes of delay.
Re: GitHub was down
#224curious if their layoffs last year had the intended impact
Re: GitHub was down
#225I see more and more people use less Github, but some other git solutions. I am afraid to think what to do when GitHub is down for hours (need to learn maillists?). Another reason is that MS may be in phase when it will ask to pay for using GitHub just for reads (rate limiter).
I recently looked into using Git in a decentralized way. It's actually pretty easy! When you would usually create a PR, you use `git format-patch` to create a patch file and send that to whoever is going to merge it. They create a branch and use `git am` to apply the patch to it, review the changes, and merge it to main. It is nice that git supports multiple remotes, though. It feels good to know that `git push` migh…
I used to work at a company with very draconian policies. Whenever I needed to update some code on a public GitHub repository, I would just push to a remote that was a flash drive. Plug it in my machine at home, pull from that remote, push to origin.
I also had to setup a bidirectional mirror back when bandwidth to some countries was restricted. We would push and pull as normal, and a job would keep our mainline in sync.
It is sad that most organizations forget that git is distributed by nature. We often get requests to setup VPNs and all sorts of craziness, when a simple push to a bare mirror would suffice. You don't even need anything running, other than SSH.
Re: GitHub was down
#226given that it seems like the entire thing is busted, can anyone explain how the unicorn page is being served?
They probably have a reverse proxy in front of all their http endpoints and that is still up and able to show the unicorn if the backends aren't responsive. The static content on the error page might also be on akami or cloudflare side.
makes sense, thanks.
the images on the page are all just base64 encoded right into the html
Re: GitHub was down
#227Github mirrors?
Re: GitHub was down
#228I've never seen an outage this big. Even the homepage doesn't load. We've had recurrent issues with Actions not running, but this seems a lot bigger. The status page says all is well, though: https://www.githubstatus.com/ . Hilarious.
Used to work ops at AWS. I don't know if it's still the case but it required VERY HIGH management approval to actually flip any lights on their "status page" (likely it was referenced in some way for SLAs and refunding customers).
Re: GitHub was down
#229This reminds me that for some reason I am logged into my gaming machine's windows store with my GitHub account thanks to the bizarre way that microsoft do auth.
Re: GitHub was down
#230I see more and more people use less Github, but some other git solutions. I am afraid to think what to do when GitHub is down for hours (need to learn maillists?). Another reason is that MS may be in phase when it will ask to pay for using GitHub just for reads (rate limiter).
emailing patches is fairly easy.
The real reason not to use github anyway though is that it's terrible (the basic "github model" for doing code review was basically made up on the back of a napkin IMO)