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

Incident with Actions – Resolved

githubstatus.com

Post reply on HN
Print view View original

71–80 of 90 posts

Re: Incident with Actions – Resolved

#71

Post by OJFord »

swed420 wrote: post #69
OJFord wrote: post #66

Earlier quoted context omitted.

That's standard for HN and explicit in the guidelines linked in the footer. No need to include the company/domain in the title, and it should match that on the submitted page. Which is 'Incident with Actions' as it reads here (now) too.

You don't see these edits happening as regularly with other submissions, though. It's not like OP is running out of space in the HN title, either. How is "Incident with Actions" more user-friendly than including "GitHub outage" in the headline? Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully?

> Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully?

Because if we follow carefully:

> If the title includes the name of the site, please take it out, because the site name will be displayed after the link.

Re: Incident with Actions – Resolved

#72

Post by swed420 »

OJFord wrote: post #71
swed420 wrote: post #69

Earlier quoted context omitted.

You don't see these edits happening as regularly with other submissions, though. It's not like OP is running out of space in the HN title, either. How is "Incident with Actions" more user-friendly than including "GitHub outage" in the headline? Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully?

> Furthermore, the subtitle of the OP is "Incident Report for GitHub," so why not just include this if we need to follow the rule so carefully? Because if we follow carefully: > If the title includes the name of the site, please take it out, because the site name will be displayed after the link.

Seems like a strange thing to prioritize, and again, quite selectively.

Re: Incident with Actions – Resolved

#74

Post by theK »

dark-star wrote: post #42
Aurornis wrote: post #32

I'm frustrated with GitHub's stability, too, but we should be clear that GitHub wasn't down. They're one of the more honest services when it comes to posting service degradations, unlike some other platforms where teams will resist updating the status page until it's an undeniable site-wide outage. > We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Ho…

I gave you an upvote, since you'll probably be downvoted into oblivion soon :-D All those "GitHub is dead" and "GitHub will crumble soon" cries are massively exaggerating things. Most users probably won't even notice these "issues" or "downtimes", since they only affect certain parts of the site. Sure, it's annoying if you're impacted, but that still doesn't spell doom for GitHub as an organization

I don't know whether Github is in trouble as an organization or whether there is a crowd just waiting for it to go down in flames and I don't care about that.

What I can attest to is that Github has been uncharacteristically flaky this past year. At least for large clients in the EU. Its not that there is outright downtime but if you have an Actions or PR invested team you probably have felt the uptick in troubleshooting these two features in the past 12 months.

And again, its not that these features go completely down, mostly its just "why is this status not being reported" or, "where is the run for this event?" And similar things. Its not that the roof fell off, its just that it is leaky and it rains and this distracts you from actually doing important things.

Re: Incident with Actions – Resolved

#76

Post by dijit »

xnorswap wrote: post #35
armanj wrote: post #16

Earlier quoted context omitted.

How reliable is this uptime? and why it's sooo different from gh's official status numbers?

Their headline figure is a bit exaggerated, it's driven from the official status numbers, but aggregates across all GH services. Imagine you run 365 services, and each goes down 1 day a year. If those are all on the same day, this would report you having 99.7% uptime. If instead, each service goes down 1 day per year but on different days, this would report you having 0% uptime. Despite the same actual downtime for a…

yeah, it's a hard problem to accurately tell people a reliablity number.

Rachel famously wrote about this in "Your nines are not my nines"[0].

The truth is though, that some systems depend on others. Actions being down means you don't merge code or release: but you know... git operations being unavailable has the same effect. It's meaningless to separate the two.

So it depends on the framing.

[0]: https://rachelbythebay.com/w/2019/07/15/giant/

Re: Incident with Actions – Resolved

#77

Post by dijit »

Instead of repeating everything again (every comment at time of writing is a rehashing of something from other threads); why not just read old threads?

We're not treading new ground anymore.

Here's a few of the better ones in the last 2 weeks;

https://news.ycombinator.com/item?id=48012022

https://news.ycombinator.com/item?id=48010301

https://news.ycombinator.com/item?id=47924775

https://news.ycombinator.com/item?id=47881672

https://news.ycombinator.com/item?id=47877644

Re: Incident with Actions – Resolved

#78

Post by fragmede »

johnfn wrote: post #24
foundatron wrote: post #4

I re-ask this: https://news.ycombinator.com/item?id=47979968 If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already? Why are you still using Github?

- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…

Turns out, the brand itself is a moat. There's never going to be another Google or Uber or Facebook or Twitter. Good or bad, GitHub is always going to have the name GitHub.

Re: Incident with Actions – Resolved

#79

Post by tardedmeme »

johnfn wrote: post #53
tardedmeme wrote: post #51

Earlier quoted context omitted.

What network effects does GitHub have? Every repository is independent. It's like saying GoDaddy has network effects.

Everyone already has an account, so there's no friction to opening up issues, adding thumbs up to issues, using the discussion forum, etc. And while I think it's pretty silly, a lot of people take "10k stars on GitHub" to be a positive signal, and you can only get there when you have 10k people willing to star on your platform.

"sign in with github" could easily achieve that

Re: Incident with Actions – Resolved

#80

Post by johnfn »

SoftTalker wrote: post #54
johnfn wrote: post #24

Earlier quoted context omitted.

- There are already viable GitHub replacements, like Codeberg, Bitbucket, Gitlab, etc. Everyone stays on Github for network effects, not because of the superior product. You can't vibe code network effects. - And yes, GitHub is a massive product with like 50 different huge features. No reasonable person would say you can trivially vibecode that. Vibecoding would still make it easier. I feel this argument is a bit sil…

Why do network effects matter for "in-house" (i.e. corporate/commercial) software work? Open-source projects, yes I can sort of get it, you want to be where the contributors are (but there are downsides to that also).

OK, say you're proposing an in-house tool to host your repo to your boss. What do you think will sound better? "Let's use this random vibecoded app I just found"? Or "Let's use GitHub"?
Post reply on HN