Ironically, I was thinking that the Github downtime is an American view in and of itself. For us living in the European time zones, Github is hardly down during our business hours. It's mostly down during US business hours, then demand is highest.
After yesterday's outage they admitted that their elasticsearch index for issues/prs lost data.
They seem to have changed the primary source of data in the issues and pull requests tabs (w/o filters applied) from the underlying database to the elasticsearch search index, which has the side effect that there's a noticeable delay between state change of an issue/pr and an update in the UI. But as seen today, these can get out of sync, and apparently they even had data loss in the index.
I would really like to know their reasoning for making that change. I can totally imagine that they wanted to "simplify" so the UI uses only a single data source instead of two.
As a user it's incredibly annoying to have a delay between issue/pr state changes and the search index picking it up.
What? React has nothing to do with current state of affairs. In fact, React on GitHub currently exists in mere islands, i.e. in Projects and recently in Pull Requests. Most of the frontend is still Web Components[1] paired with Turbo[2] for hot reloading. GitHub is still as slow even with JavaScript disabled, try it yourself. Backend just serves stuff really slow. In fact, there is an alternative GitHub frontend (no affiliation) that feels snappier and is written in React.[3]
With that said, Mitchell complains about outages. These started directly after Microsoft acquisition[4] and are attributed to migration from AWS to Azure.
Pull Requests is the thing that was wacky in the UI yesterday, coincidence or not? I have no idea.
Yesterday we saw PR pages that displayed no error, just displayed wrong info. I would have preferred to get an error page than outdated or empty lists. I was guessing this was related to the React migration but I don't really know.
Also, the browser back and forward buttons no longer work in pull requests when going between PR tabs (commits, checks, files changed, etc) as well as some other site interactions.
Like, what user-hostile intention was the reasoning behind that? I am literally imagining a product manager smoking a cigar and laughing at the RUM session replays of me losing my shit.
> They call us warmongers and then wonder why we don't want to help them fight their war.
There is a huge difference between attacking foreign nations because of oil... Oh, pardon me, because of... Geopolitical interests... Oh, pardon me... In the name of democracy and self-defense when you're being attacked (such as Ukraine).
We came to help you after 9/11, when for some reason you invaded Iraq although Osama Bin Laden and Al-Qaeda had taken responsibility...
But sure, think that you're white guardians of the flame of freedom and democracy all you want!
You're in exactly the same ballpark as China and Russia, they're just without the Hollywood propaganda.
Over said decades I've worked on countless (open source) projects there.
Professionally? 1 project in all those years. Yes, exactly 1 (still there).
Every single other project was either in bitbucket, gitlab, gitea, forgejo or... I am sure I forgot some forge.
What I am trying to convey is: fascinating how "everything is on GitHub" is a very american way to see the world.
reply