Incident with Issues and Pull Requests(githubstatus.com)
githubstatus.com
Incident with Issues and Pull Requests
https://www.githubstatus.com/incidents/nf7s6933tnn8
142 comments
in CET they're more around afternoon coffee break time
How i miss the euro lifestyle
What is going on over there? Third day in a row is... kind of impressive.
Lots of copilot generated code failing
Not only Copilot, seems like some Microsoft services like Bing AI and Bing Image Creator have some issues today as well with 4xx / 5xx, and incorrect region authorization (had to switch the account region from a European country to US to make it work again on mobile)
I think you may have missed the joke - they were implying Github was using Copilot internally, causing the outages, due to poor output. Not that Copilot itself was unavailable (although that may be true, also)
They blamed the march and april outages on some database query that was changed due to an infrastructure change they rolled out. I'm guessing their infrastructure change caused some other race condition issue that they are only seeing after major production failure due to not load testing enough in their staging environment https://github.blog/2023-05-03-github-availability-report-ap...
As much as I’ve been frustrated by these outrages, we’ve all been there
My money is on some significant backend architecture migration gone wrong without a viable way to roll back the time machine :)
Feels like an organization as big as Microsoft must surely have some sort contingency plan in place before doing such a large migration. Right?
Sales handing out Office365 discounts and trying to convince people that AWS and GCP is going to steal their data, judging by companies I worked for that used Azure.
Wasnt it true? Thas Amazon abused their AWS position and stole their competitors data, so thats why Germany's retail businesses are building their own Clouds
Any links? Interested on reading more about this
Here’s one
https://www.wsj.com/articles/amazon-scooped-up-data-from-its...
The gist is that yes it’s true. They’d come out with their own Amazon Basics branded stuff and push it to the top.
https://www.wsj.com/articles/amazon-scooped-up-data-from-its...
The gist is that yes it’s true. They’d come out with their own Amazon Basics branded stuff and push it to the top.
But that's amazon, not AWS.
I worked on the volume licensing part of Microsoft years ago and deployments were stressful. They'd start at friday late like 8pm or so and go until 8am in the morning. Everyone was on a long call the entire time. I hated it.
At that point, I wondering if that's not me just because I updated some libraries on my local build agent.
Azure?
Just another day doing DevOps for a Ruby on Rails product.
Today seems worse than yesterday. I'm getting wildly inconsistent results when viewing repositories after a push. Hard to tell if my push actually went through, and it's not triggering actions.
exact same issue
It comes in around 09:30 on US east coast.
I suspect that it's related to high load.
I suspect that it's related to high load.
Maybe they fired too many people this time? https://news.ycombinator.com/item?id=35334705
From an SRE, one of their DB clusters failed. They use Vitess which is great, but it can be prone to hotspots and doesn't auto-shard. Heavy usage (esp. from large customers, rogue jobs) can take down the cluster. When it goes down, it's a PITA to resolve.
This literally isn't true and looks awfully like the talking points of one of our competitors.
Ah, unbalanced shards via wrong sharding keys was an issue at one point, IIRC. I remember talking with an SRE there when something bad happened at GitHub last year, and I know that this time the current DB cluster failed.
To be clear, I _was_ mapping previous incidents with this year's incident — no competitor or hard feelings involved. I really like Vitess, fwiw. And the only thing I really love is FoundationDB :)
To be clear, I _was_ mapping previous incidents with this year's incident — no competitor or hard feelings involved. I really like Vitess, fwiw. And the only thing I really love is FoundationDB :)
That wasn't clear.
Side note: "Autosharding" is largely a myth that unproven databases are touting. Sharding is complex and requires planning and control. Databases that start shuffling data round without oversight produce nasty surprises. Trying to be too magic is normally always a mistake with databases.
Side note: "Autosharding" is largely a myth that unproven databases are touting. Sharding is complex and requires planning and control. Databases that start shuffling data round without oversight produce nasty surprises. Trying to be too magic is normally always a mistake with databases.
Yeah, fair, totally get it. Wasn't aiming to spread FUD, and I know that FDB is a little hard to compare against... it is pretty magic with how it routes and shards :D (https://forums.foundationdb.org/t/keyspace-partitions-perfor...)
For posterity: https://github.blog/2023-05-16-addressing-githubs-recent-ava...
It was the DB, and it was rogue usage on May 10, so I'm standing by my original comment
It was the DB, and it was rogue usage on May 10, so I'm standing by my original comment
What would you know, random Hacker News commen--oh. Hi Sam, carry on.
<3 Hey Sarah!
I'm considering host a gitea instance backup all of my repos.
I have an important fix that need to be deployed right now but there is no way to deploy it in a normal way with our CI which one was setup with Github Action. Fortunately I have a instruction to bypass CI and build the source by myself.
But again, Github defeat me because our release workflows are depend on GitOps which are effected by Github issue. Ahhhhhhhhhh I have to build the docker image, push it to ECR then update a YAML template to make EKS apply the new changes
It's 9PM in my timezone and I'm waiting for my patches are up. A frustrating incident
I have an important fix that need to be deployed right now but there is no way to deploy it in a normal way with our CI which one was setup with Github Action. Fortunately I have a instruction to bypass CI and build the source by myself.
But again, Github defeat me because our release workflows are depend on GitOps which are effected by Github issue. Ahhhhhhhhhh I have to build the docker image, push it to ECR then update a YAML template to make EKS apply the new changes
It's 9PM in my timezone and I'm waiting for my patches are up. A frustrating incident
Gitea's ability to create a local repository as mirror of a remote repository is great for this. You can stay on Github and have your code regularly mirrored locally.
If only Git had this sort of functionality built in…
Pretty sure git can not continuously pull/push the mirrored repo like this feature does, by default every 10 minutes.
Gitea can run your CI actions too, and host your releases.
I have this setup running on a Synology NAS at home. I'm currently syncing all of my starred github repos to local storage using a short bash script that runs once a week. Once a repo is in gitea, it pulls any new updates from github every 6 hours or so. It's mostly for archival purposes, just in case something majorly bad happens to github.
Would you share your setup?
I'm interested in building the same but if yours already works well then I see no point in duplicating important work.
I'm interested in building the same but if yours already works well then I see no point in duplicating important work.
Sure!
Here's a gist to the script: https://gist.github.com/sklarsa/845152721ee9292eb01f70756b89...
As for gitea, I'm just hosting it using Docker and orchestrating using a simple docker-compose file that maps the gitea data directory to a Volume on the synology: https://gist.github.com/sklarsa/0dd6d6094dac6bf6e7bf61df9ca5...
It's all hosted on my private network at home.
Here's a gist to the script: https://gist.github.com/sklarsa/845152721ee9292eb01f70756b89...
As for gitea, I'm just hosting it using Docker and orchestrating using a simple docker-compose file that maps the gitea data directory to a Volume on the synology: https://gist.github.com/sklarsa/0dd6d6094dac6bf6e7bf61df9ca5...
It's all hosted on my private network at home.
Or use Gitlab. I remember doing a mirror syncing from Github with one of my gitlab repository. The main reason I used to do it is Gitlab offer free built-in CI at that time
In my case one of most important thing is the GitOps workflow. It's single source of truth so it's also single point of failure ;(
Daily reminder that https://github.com/MichaelMure/git-bug could use some help :-D
Unfortunately, I can't see what this is because GitHub is down.
... of course. Mirror there: https://gitlab.com/MichaelMure/git-bug
I was greeted with a "Please give us this UUID when you report this bug" twice and I thought it was a Github breaking repo. love it
So nice to meet you all here again, gents - this is becoming a regular thing.
We are back to Windows 95, which reliably crashed after 49.7 days:
https://www.cnet.com/culture/windows-may-crash-after-49-7-da...
https://www.cnet.com/culture/windows-may-crash-after-49-7-da...
> Codespaces is experiencing degraded performance. We are continuing to investigate.
Imagine not only not being able to push your code, but also not even being able to _write your code_ at all. And so many orgs rely on Actions to even be able to deploy. Geez. I personally believe that the cloud sucks.
Imagine not only not being able to push your code, but also not even being able to _write your code_ at all. And so many orgs rely on Actions to even be able to deploy. Geez. I personally believe that the cloud sucks.
If you're putting all your eggs in one basket you are the only one to blame I guess.
It's sill weird to me how many and how much companies relly on Github infra.
It's sill weird to me how many and how much companies relly on Github infra.
Not just issues and PRs - I had to try multiple times before I was able to successfully push code to a repo over SSH.
This is the error I was seeing:
This is the error I was seeing:
ERROR:
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.Everyone thinking they've been laid off and notified via git push. Just GitHub being GitHub.
Yeah, same. I've since been able to push my branch, but now I can't open a PR.
Anecdotal - I've been using Gitlab for a few years on some projects, and haven't experienced any downtime issues with them of this magnitude.
Yeah, Gitlab has had its share of downtime. Github has had shockingly little until the last year or two. These things come and go.
Of course, if this continues happening it may be time for the OSS community seriously consider migrating en masse.
[Edit to fix grammar - thanks for the corrections!]
Of course, if this continues happening it may be time for the OSS community seriously consider migrating en masse.
[Edit to fix grammar - thanks for the corrections!]
Apologies to be pedantic, I think it's en masse.
FWIW the typical phrase is "en masse" (which is French). The English translation is "in mass".
The English translation would be something like, “all together, at the same time”. “In mass” isn’t an English idiom.
"en masse" is the term used in English as well.
Yep, just noting for anyone who may not realize that "in mass" isn't really a thing in English.
As you note, en masse is common — enough so that you even don't need to italicize it (although you can).
As you note, en masse is common — enough so that you even don't need to italicize it (although you can).
If you're brave enough, you can italicize whatever you want.
Indeed. Tips on when you should italicize foreign words in English writing: https://proofed.com/writing-tips/should-you-italicize-foreig...
I can still remember https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab... (though I can't rembember reading of any big problems since then)
Same. Overall, I like GitLab a lot more than GitHub. I wonder how much of GitHub's popularity is buoyed by its status as the defacto home for OSS
It has good parity with GitHub on core functionality and a generous free tier.
To be fair, Gitlab accidentally deleted 6 hours worth of data from their database some time ago.
Three days in a row of outages, in less than a week of unreliability after yesterday's downtime of GitHub Actions [0].
Really at this point, you just might as well consider self hosting and it is looking very chronic with GitHub falling apart and self-hosting was indeed the sensible idea just like how the other open source projects have done for years.
GitHub is going just great, and centralizing everything to GitHub really was a good idea wasn't it? [1] /s
[0] https://news.ycombinator.com/item?id=35887029
[1] https://news.ycombinator.com/item?id=22867803
Really at this point, you just might as well consider self hosting and it is looking very chronic with GitHub falling apart and self-hosting was indeed the sensible idea just like how the other open source projects have done for years.
GitHub is going just great, and centralizing everything to GitHub really was a good idea wasn't it? [1] /s
[0] https://news.ycombinator.com/item?id=35887029
[1] https://news.ycombinator.com/item?id=22867803
There's no way a company could run its own source management system and have an uptime approaching 23 hours a day -- that's like one nine of uptime!
(/s of course)
(/s of course)
Shout out to all devs that put the deps of their programs on GH...
Right now I can ignore that my PRs show 500 error, or old code best case scenario.
But... I cannot build and ship due to project's dependency depending on some stuff hosted on GH.
Right now I can ignore that my PRs show 500 error, or old code best case scenario.
But... I cannot build and ship due to project's dependency depending on some stuff hosted on GH.
Hugs to the GitHub Opps and SRE teams right now!
Also hugs to any Devs, Opps or SREs directly effected by this outside GitHub.
Looking forward to a post-mortem on the last few days, I'm sure it will be a really interesting read.
Also hugs to any Devs, Opps or SREs directly effected by this outside GitHub.
Looking forward to a post-mortem on the last few days, I'm sure it will be a really interesting read.
Third day in a row this has affected my productivity
500's on every repo page + CLI errors on pull / push. Completely useless at the moment.
Anyone experienced with asking for service credits for enterprise customers? It looks like you have to prove that they have missed their SLAs
I've had some actions queued for multiple days now on certain repos, but not others. I've cancelled them and restarted them during the green status intervals but they all go back to "Queued". I've also cancelled them and then made slight documentation tweaks to get new commit hashes on the branches and it still goes to queued.
Just lost a merge commit to dev/null. This is getting tiresome
How??? You do the merge, which either creates a new commit for the change, or appends the commits to your existing tree. Then you push that to the remote. If the push fails, you can just push again, it's not lost. And if the merge failed, you didn't have any merge commit to begin with.
There used to be a pretty consistent bug that if an on-site PR merge failed but you clicked "Retry", that it just did a basic non-squash full-merge discarding all your commit message work, often requiring a revert to tidy things up. It could be similar to that.
May have been using the GitHub interface
You can do a lot of operations on the github web UI nowadays. Could have been that
I'm going to self-host my git repos. Any recommendations?
The git+nginx would suffice but it does not offer GUI. I need one to see the changes proposed (aka PRs).
Gitea is nice, but a bit overkill for my needs. I don't need CI, files hosting, issues, team members, releases, wiki, forking/watching/staring, etc.
The git+nginx would suffice but it does not offer GUI. I need one to see the changes proposed (aka PRs).
Gitea is nice, but a bit overkill for my needs. I don't need CI, files hosting, issues, team members, releases, wiki, forking/watching/staring, etc.
Gitea is pretty light on resources so even though it has a extra functionality you don't need it's not really a resource pig. Unlike say, GitLab.
Gitea requires a database which is unwanted feature for "git server" in my little world.
I'm just looking for "website" (read: interface) that list files over HTTPS, with the ability to show nice looking diffs. Some sort of ssh keys(?) to prevent unauthorized access etc.
I'm just looking for "website" (read: interface) that list files over HTTPS, with the ability to show nice looking diffs. Some sort of ssh keys(?) to prevent unauthorized access etc.
Maybe something like gitweb? https://git-scm.com/docs/gitweb
I have not used it before, but it seems like it follows your requirements (Except auth using SSH keys maybe, but that could be a task for e.g. Nginx)
I have not used it before, but it seems like it follows your requirements (Except auth using SSH keys maybe, but that could be a task for e.g. Nginx)
Thanks, I discovered "git instaweb" which is based on gitweb. It's nice and offers mostly what I'm after,but the 100% layout width is terrible (no opt to configure it).
Maybe something like gitolite then?
https://github.com/sitaramc/gitolite
I've not used it personally though, so no idea how well it works in practise.
https://github.com/sitaramc/gitolite
I've not used it personally though, so no idea how well it works in practise.
Thanks! Gitolite doesn't offer any UI for what I see. Also to set it up is too complicated.
I just found about "git instaweb" (developed by Git authors, but it's extra OS package) - it works locally, probably what I was looking for (minus the 100% width page layout).
BTW There's Gitblit is someone's fancy hosting Java app.
I just found about "git instaweb" (developed by Git authors, but it's extra OS package) - it works locally, probably what I was looking for (minus the 100% width page layout).
BTW There's Gitblit is someone's fancy hosting Java app.
> going to self-host my git repos. Any recommendations?
Depending on your needs, this can be as simple as sticking repos on any server you have and cloning/pulling/pushing over ssh. If you want something more sophisticated, though, there's a handful of nice applications (gitea is being suggested further up-thread).
Depending on your needs, this can be as simple as sticking repos on any server you have and cloning/pulling/pushing over ssh. If you want something more sophisticated, though, there's a handful of nice applications (gitea is being suggested further up-thread).
imho Gitea is so smooth to deploy and manage that it's worthwhile even if you don't need its advanced features.
this is the third day in a row this is a problem yet they're framing it as a new outage.
I'd say it's reasonable to list it as separate outages on the status page as it's really a representation of "is github available and working as expected". Even if it is the same issue, when they manage to mitigate it (or it goes away) I'd want to see that everything is now available from a user perspective.
That said, they're getting to the point where they really need to make some larger post about this. It seems reasonable to assume it is all from one root cause.
That said, they're getting to the point where they really need to make some larger post about this. It seems reasonable to assume it is all from one root cause.
Loading github.com is returning a 500 for me currently, so seems like more than just issues/pull requests. Also seeing actions fail with 500s on assorted steps.
Similar issues for me. I can load github.com and my profile, but visiting a repository (or trying to git pull a repo with the https origin) returns a 500.
It started for me a few minutes before the status page showed something. Which is understandable, of course.
But strange that it keeps happening almost every day now.
But strange that it keeps happening almost every day now.
I can confirm this as well. I started seeing 500 errors intermittently when trying to view pages, so I checked status page and saw everything was green. Status page started showing the incident within about 3 minutes of when I started seeing issues. Clearly that's all based on happenstance of when I was landing on GitHub's website, but I have found that of all the status page's by large companies, GitHub's is almost always showing an incident as soon as I start noticing issues myself.
Yeah, I was getting 500s for about three minutes before they posted the status update. I guess it's good that they at least update the status page in a timely fashion, but the third day in a row of downtime is not exactly good service.
Have to give it to them for how useful their status page is. Other products we use play all kinds of word games to downplay issues so they don't have to show them on the status page, which is extremely annoying.
Does anyone host their own git repos in an enterprise environment? How do you do it and what are some good resources for learning how to do this?
Yes, we do this using https://gitea.io/en-us/ on a private server (firewall, backups and a replica) for most projects. Github is only used when it's required by a stakeholder.
Are you interested in spinning up an entire CI environment? or something where anyone can push a branch to a file based mirror?
There are aspects of permissioning that the cloud git repo providers have that become more challenging to implement as a home grown solution and unless you have the resources to maintain it, it also becomes interesting.
On one hand, you can do `git clone --mirror` and you'll have a copy of the repo and put that on a file share... though there's no permissions or automatic syncs for it (or CI). If you want those, then you get into some development (and maintenance) of the git hooks.
Going to things like a local hosted gitlab instance means that you need to have a local docker hosted environment running, and someone to maintain that, and the storage for it, and all of the other fun that comes with administering a complex 3rd party application on prem. When things are going good, it's an hour or two a week... when something breaks its several hours with calls to support (you're using a paid / licensed version to get support... right?) from someone who has a sysadmin skill set rather than a developer skillset. And don't forget about DR.
There are aspects of permissioning that the cloud git repo providers have that become more challenging to implement as a home grown solution and unless you have the resources to maintain it, it also becomes interesting.
On one hand, you can do `git clone --mirror` and you'll have a copy of the repo and put that on a file share... though there's no permissions or automatic syncs for it (or CI). If you want those, then you get into some development (and maintenance) of the git hooks.
Going to things like a local hosted gitlab instance means that you need to have a local docker hosted environment running, and someone to maintain that, and the storage for it, and all of the other fun that comes with administering a complex 3rd party application on prem. When things are going good, it's an hour or two a week... when something breaks its several hours with calls to support (you're using a paid / licensed version to get support... right?) from someone who has a sysadmin skill set rather than a developer skillset. And don't forget about DR.
Yes, primary on Gerrit, backup replica to $wherever. Bonus: actually usable code review platform.
You can just use GitHub Enterprise if you want GitHub, but self-hosted.
Yes using gitolite, it just works.
In the past I worked at a company which used the commercial solution from JFrog, I don't remember ever having problems with git availability as a user.
In the past I worked at a company which used the commercial solution from JFrog, I don't remember ever having problems with git availability as a user.
At a previous employer we used gitea along with jenkins.
This gives me some the fail-whale vibes. But the blue bird didn't fail like this these days, strangely.
Have they said what has been up lately?
They are far overdue for issuing a statement.
They're having so many outages that they've moved from making statements after each event to aggregating them all and write about all of them on a month-by-month basis.
I'm not joking: https://github.blog/tag/github-availability-report/
I'm not joking: https://github.blog/tag/github-availability-report/
They've had that for years.
I don't remember when it started getting worse, but if I do a guess, I'd say around 2018 sometime, which I'd also guess is when they started pushing more changes too.
I feel that with dynamic like this, someone could make a page showing the number of days since the last github incident.
It would show a very prominent zero and be a static page with no logic whatsoever.
It would show a very prominent zero and be a static page with no logic whatsoever.
Yup, hitting me and all over twitter: https://twitter.com/search?q=github
Trying to access repos is returning 500 for me also
Very helpful 500 page: "In the meantime, try refreshing."
Maybe they should put CoPilot in charge of ops...
I wasn't even able to get to repos or users/orgs for a while (though as I write this it seems like that is coming back).
and i thought i broke `master`...
git says my code pushed fine and everything is synced, but Github is not showing any of my changes.
Edit: 10 minutes later, the Github finally shows the push, but triggers still aren't working.
Edit #2: Things are working normally now.
Edit: 10 minutes later, the Github finally shows the push, but triggers still aren't working.
Edit #2: Things are working normally now.
Another day, another outage. I'm getting 500 for any repo.
Thee days in a row!! Is this the result of all the job cuts?
Is it time to move back to Jenkins? :X
Now that gitea supports act_runner (and hence a reasonably usable clone of GH actions), Jenkins is dead.
Oh, that's really good news. :)
[deleted]
I cannot even push code
Here we go again…
Back to biz
[deleted]
On the bright side, maybe, just maybe the open source community realises that such centralisation might not be the best solution for hosting code.
It's a feature, not a bug!