GitHub incident: ongoing issues with Actions, Issues and other Git operations • Hacker News Board

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#81

Post by capableweb » Tue, May 09, 2023, 1:31 PM UTC

RamblingCTO wrote: post #73

Hm, we had this last week as well. Guess who had a demo yesterday, needed to deploy things on Thursday/Friday and couldn't :(

If this is your first time being affected, I guess you have a good reason to adjust your deployment structure so you can deploy manually if needed.

If this is not the first time, hopefully at least it will be the last one :)

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#82

Post by rvz » Tue, May 09, 2023, 1:31 PM UTC

Once again another GitHub incident and 4 days later before the last one [0], GitHub Actions goes down.

You are better off self-hosting at this point, rather than centralizing everything to GitHub [1] as it is just chronically unreliable for years ever since the Microsoft acquisition.

[0] https://news.ycombinator.com/item?id=35817998

[1] https://news.ycombinator.com/item?id=22867803

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#83

Post by capableweb » Tue, May 09, 2023, 1:32 PM UTC

dindresto wrote: post #70

candiddevmike wrote: post #30

Really 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.

Did you try the macOS runners? Been using Linux, Windows and macOS runners without any issues for quite some time.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#84

Post by hnarn » Tue, May 09, 2023, 1:32 PM UTC

RamblingCTO wrote: post #73

Hm, we had this last week as well. Guess who had a demo yesterday, needed to deploy things on Thursday/Friday and couldn't :(

Maybe a good time to investigate whether it's possible to hold those demos without relying on third party services.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#85

Post by hnarn » Tue, May 09, 2023, 1:33 PM UTC

candiddevmike wrote: post #30

Really looking forward to kicking the tires on Gitea next month.

Any reason to use Gitea over the Forgejo fork? Based on the drama I'd rather use Forgejo if they're functionally equal.[1]

[1]: https://forgejo.org/faq/#why-was-forgejo-created

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#86

Post by meindnoch » Tue, May 09, 2023, 1:35 PM UTC

smcleod wrote: post #57

meindnoch wrote: post #25

Thankfully git is a distributed version control system, so such outages are not of major concern.

You're kidding right? People / companies rely on git being available for deployments, builds, config changes, developer workflow etc

But "git" is available. It's most likely under /usr/bin.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#87

Post by hnarn » Tue, May 09, 2023, 1:36 PM UTC

8organicbits wrote: post #72

lol768 wrote: post #16

Earlier quoted context omitted.

It's definitely no less reliable than GitLab, where a good 300GB of database data got deleted in production by accident...

gitlab.com or self-hosted?

gitlab.com is implied since it happening on a self-hosted instance would have nothing to do with gitlab as a service (they can't be responsible for your on-site backups).

> Trying to restore the replication process, an engineer proceeds to wipe the PostgreSQL database directory, errantly thinking they were doing so on the secondary. Unfortunately this process was executed on the primary instead. The engineer terminated the process a second or two after noticing their mistake, but at this point around 300 GB of data had already been removed.

https://about.gitlab.com/blog/2017/02/10/postmortem-of-datab...

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#88

Post by __alexs » Tue, May 09, 2023, 1:37 PM UTC

wun0ne wrote: post #3

Does GitHub provide uptime stats? Seems very unreliable recently.

Performance of the GitHub website in general feels increasingly bad.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#89

Post by hnarn » Tue, May 09, 2023, 1:37 PM UTC

p-o wrote: post #63

shibel wrote: post #60

Rumor 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.

"Always"? I don't remember it being nearly as frequent before they were bought by Microsoft, some data to back this up would be nice.

Re: GitHub incident: ongoing issues with Actions, Issues and other Git operations

#90

Post by smcleod » Tue, May 09, 2023, 1:38 PM UTC

meindnoch wrote: post #86

smcleod wrote: post #57

Earlier quoted context omitted.

You're kidding right? People / companies rely on git being available for deployments, builds, config changes, developer workflow etc

But "git" is available. It's most likely under /usr/bin.

It's not git people are paying for.