Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub was having issues

githubstatus.com

Post reply on HN
Print view View original

31–40 of 96 posts

Re: GitHub was having issues

#31

Post by 1337shadow »

toomanybeersies wrote: post #28
rvz wrote: post #5

Here we go again [0] and again [1] and again [2] and again [3]. Time to reset the counter once again. Now everything there is degraded performance. Oh dear. Consider a self-hosted alternative or have one as a backup like I have said before. [0] https://news.ycombinator.com/item?id=27192869 [1] https://news.ycombinator.com/item?id=27172443 [2] https://news.ycombinator.com/item?id=26666843 [3] https://news.ycombinator.…

> Consider self-hosted alternatives like I have said before. This assumes that your self-hosted Git service will have better uptime than Github.

> This assumes that your self-hosted Git service will have better uptime than Github.

Piece of cake. But it will also have better performance.

Re: GitHub was having issues

#32

Post by 1337shadow »

gjulianm wrote: post #26
thinkindie wrote: post #13

Earlier quoted context omitted.

self hosted won't insulate you from your VCS instance failing. I used to work at a medium-sized company with Gitlab 8 years ago, it was running into several issues and required frequent maintenance.

To give another data point, in my company we're running Gitlab (we started 3,4 years ago maybe?) with some pretty heavy use of CI and we've had no issues, even with automatic upgrades enabled (we have tested backups, we're not crazy).

Confirmed, on a ubuntu host GitLab is actually the product that I have the best self hosted experience with. Apt packages running their Chef Cookbooks always impressive!

Re: GitHub was having issues

#34

Post by latch »

toomanybeersies wrote: post #17
beermonster wrote: post #6

For people using GitHub Actions how often do these types of incidents impact your CI/CD?

Since most CI systems pull code from Github, it impacts other CI providers as well.

Most?

I'd wager that there's more self-hosted CI's running code from self-hosted repositories than from GitHub (however you measure it: e.g., lines of code, build time, etc)

Re: GitHub was having issues

#35

Post by terramex »

Kiro wrote: post #3

OT but why did it capitalize the title like that? I submitted "GitHub is having issues". I don't see that for other submissions (unless people manually edit them afterwards). EDIT: Before the change to "GitHub was having issues" it had converted my original submission from "GitHub is having issues" to "GitHub Is Having Issues".

It is title case: https://en.wikipedia.org/wiki/Title_case

Re: GitHub was having issues

#36

Post by toomanybeersies »

ljm wrote: post #15
Tainnor wrote: post #8

Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253 )

A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now. However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range. That has to be an utter misery for anyone who's on call.

Makes it much harder for enterprise customers to claim on their SLA as well.

Re: GitHub was having issues

#37

Post by Raed667 »

Kiro wrote: post #3

OT but why did it capitalize the title like that? I submitted "GitHub is having issues". I don't see that for other submissions (unless people manually edit them afterwards). EDIT: Before the change to "GitHub was having issues" it had converted my original submission from "GitHub is having issues" to "GitHub Is Having Issues".

I also find myself writing titles in a "Title Case" like that. It is a habit I got from the days when I used to blog.

Re: GitHub was having issues

#38

Post by threeseed »

Tainnor wrote: post #8

Maybe these are just a bunch of coincidences, but I have a feeling that GitHub is being poorly run recently. Apart from quite frequent uptime issues, it seems that Github Actions is pretty half-baked and they completely botched the migration of Dependabot (for example, take a look at this issue and especially, how it was handled: https://github.com/dependabot/dependabot-core/issues/3253 )

They have also largely abandoned their Terraform and Jira integrations.

Has been left up to the open source community to implement basic functionality.

Re: GitHub was having issues

#39

Post by sverhagen »

toomanybeersies wrote: post #36
ljm wrote: post #15

Earlier quoted context omitted.

A shame they removed all their uptime graphs on the status page, since it's much harder to get a read on things now. However, scrolling back through the status page's history for the last year shows that there between 6 and 12 incidents every month, and it often hovers at the high end of that range. That has to be an utter misery for anyone who's on call.

Makes it much harder for enterprise customers to claim on their SLA as well.

...so that customers start tracking it themselves, so that everyone can waste time on discussing their differences in numbers and measurements, and who is right and who is wrong.
Post reply on HN