Rumor has it Microsoft is pushing them to move their infrastructure to Azure, which explains much of the frequent downtimes lately.
Where'd you get this from?
GitHub incident: ongoing issues with Actions, Issues and other Git operations
61–70 of 130 posts
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#62If that makes you mad, I still need help with https://github.com/MichaelMure/git-bug ;-)
Coming at some point, kanban and pull-request support, offline-first!
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#63Rumor has it Microsoft is pushing them to move their infrastructure to Azure, which explains much of the frequent downtimes lately.
Maybe it's the case, but Github has always had issues with uptime and stability.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#64I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters w…
This is why I don't touch other people's keyboards.
Well from another perspective, a bootstrapping perspective, and hackernews does like a bootstrapping perspective, I could make a case that a good meal could pick licked out of most keyboards, saving money on lunch once a week.
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#65Rumor has it Microsoft is pushing them to move their infrastructure to Azure, which explains much of the frequent downtimes lately.
Where'd you get this from?
1) A friend in DevOps who supposedly has contacts there.
2) It's not like this push is a big secret: https://www.cnbc.com/2022/10/12/microsoft-github-relying-mor...
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#66From the outside, it appears GitHub doesn't have any internal sharding going on.
Outages always affect _all_ repos.
Architecturally this seems rather sub optimal?
EG AWS doesn't roll out changes globally - they start with an internal shard within a region and progressively roll out to more shards and more regions.
Why do GitHub not do the same?
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#67From the outside, it appears GitHub doesn't have any internal sharding going on. Outages always affect _all_ repos. Architecturally this seems rather sub optimal? EG AWS doesn't roll out changes globally - they start with an internal shard within a region and progressively roll out to more shards and more regions. Why do GitHub not do the same?
last I heard they've sharded some stuff, but some of the core tables/databases are still using a monolithic architecture.
And I guess you're only as strong as your weakest link, which can be not that bad, that is, if it isn't your core tables.
Though take this with a grain of salt, this is mostly hearsay =D
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#68"Actions, Issues" are not "Git operations". would sound better without "other" in title
good catch
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#69I debugged for one min at 11:59 trying to push, and then my eat-lunch notification came in at 12:00 and I opened hackernews with a tuna sandwich and this is super helpful because it means I wont need to debug it locally for 10 mins before figuring out Github is down. Edit - Just want to clarify when I say "opened hackernews with a tuna sandwich" I want to clear up that I did indeed full on mash the keyboard letters w…
Easy to fix just adjust your system prompt add the following:
“Never ever type on keyboard with sandwich not even the most delicious tuna sandwich”
Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations
#70Really looking forward to kicking the tires on Gitea next month.
We've switched to selfhosted Gitea last month, no regrets. Only the CI story could be a bit better. We're currently using Woodpecker but need macOS runners, and Woodpecker's "local" agent implementation is still unstable. I'm watching Gitea Actions' progress with great interest.