Live data from Hacker News

Incident with Actions and Pages

githubstatus.com

311–320 of 407 posts

Re: Incident with Actions and Pages

#311
post #42

Earlier quoted context omitted.

No, it doesn’t. Their competition is not similarly unstable, despite existing in the same world of LLMs. Think critically.

Devil’s advocate, Pareto heuristic would let us speculate that 80% of LLM traffic would be aimed directly at the largest provider, i.e. GitHub.

Isn't the relative increase more of interest? If someone was only owning 10% of the market, and they've only gotten 8% (percentage points) of the 20%-not-GH LLM-related increase, they'd still be seeing a very similar spike compared to their baseline as GitHub.

Re: Incident with Actions and Pages

#312

Not reflected on GitHub Status: most of the frontier models disappearing from most people's subscriptions: https://www.reddit.com/r/GithubCopilot/comments/1toa9tf/mode...

Meanwhile people using a copilot proxy [1] with a third party harness have zero issues. Very clumsy enforcement if not a bug.

[1] https://github.com/ericc-ch/copilot-api

Re: Incident with Actions and Pages

#313
post #62

Earlier quoted context omitted.

All these monitoring rules are of the format "when 500 errors > baseline for x minutes". Otherwise you'd have monitoring alerts every second. So it is normal for users to already see errors before github officially counts it as an outage.

I'm not arguing with what you're saying, but it does make me wonder: What exactly is the point of the status page, if "it is normal for users to already see errors before GitHub officially counts it as an outage"? Is it more so to have something to link to for managers who aren't using the service have a pretty bar to look at and feel like they are "doing something"? Or is it more of a kind of a way to prevent confir…

There is oddly enough a middle ground between "zero errors whatsoever" and "outage".

Re: Incident with Actions and Pages

#314
Microsoft is really working hard to kill off GitHub now. That's quite amazing.

We have already seen this in the last some weeks, but now this has become a meme that keeps on giving. GitHub down! GitHub up again. GitHub Down! GitHub ... ...

Re: Incident with Actions and Pages

#315

We’ve had GitHub actions for long enough, it’s time for GitHub consequences.

I think this can only happen if there are viable alternatives.

For instance, the UI at setups such as https://git.devuan.org/Daemonratte/gtk2-ng is quite ok-ish, in my opinion. Granted, it is mostly copy/paste from github but that still is about 1000000x better than sourceforge's interface - and gitlab's UI too (I just hate gitlab's UI, they seem to love complexity and a billion features only 0.000001% ever need; GitHub, with all its faults, is for the most part really simple - not everywhere, e. g. GitHub wiki setup sucks, but by and large I think it is simple overall).

Re: Incident with Actions and Pages

#316
As an Indy hacker I want to see GitHub succeed, but I ditched actions years ago - (shocking) false economy. Spend entire nights pushing to actions over and over only for complaints about weird/niche dependency issues and other oddities - the cycle time's just too slow and the DX is no fun (my pain doesn't even factor in outages; just the feature itself as it's intended to be experienced). I want to spend time talking to users and building features, not debugging weird syntax or dependency issues on a remote machine non-interactively.

So why are Actions so unreliable anyway? Occam's Razor would probably suggest the domain is inherently complex/difficult; but other providers show that reliability is possible. What would Occam's Razor suggest next? Poor management..?

Re: Incident with Actions and Pages

#317
post #257

Earlier quoted context omitted.

Because scaling complex systems is not trivial

It was pretty easy before October 2018, when Microsoft bought them: https://www.githubstatus.com/uptime?page=31

To be fair, that was 8 years ago. Github now has all that days and users + 8 years of data and users.

Re: Incident with Actions and Pages

#318

Earlier quoted context omitted.

People should use something that keeps a local copy of their code and just copies it to Github and to other contributors with a sync process to push and pull changes. Some sort of 'distributed source control system' maybe. Then people would only need a 'hub' to connect to people, and it'd be easier to move somewhere else.

This gets tiresome. Github is a lot more than a host for Git repositories. If you want to suggest that people use something else, you need to suggest a replacement that has the features people use Github for.

yeah, #1, it is free private file storage, and #2, it's a download portal for free as in beer software replacing paid offerings. that's what it is for 99.99% of people.

being a host for git repositories has never been its core competency. neither has its groupware offering.

does it even serve OSS well? a very interesting criteria is, "Have mature or adopted end-user-facing OSS recently merged a large PR from an unallied contributor?" The answer is overwhelming no. This is why there is so much innovation in this space.

Re: Incident with Actions and Pages

#319
post #316

As an Indy hacker I want to see GitHub succeed, but I ditched actions years ago - (shocking) false economy. Spend entire nights pushing to actions over and over only for complaints about weird/niche dependency issues and other oddities - the cycle time's just too slow and the DX is no fun (my pain doesn't even factor in outages; just the feature itself as it's intended to be experienced). I want to spend time talking…

What did you switch to, and what do you like about it?

Re: Incident with Actions and Pages

#320

We’ve had GitHub actions for long enough, it’s time for GitHub consequences.

I think this can only happen if there are viable alternatives. For instance, the UI at setups such as https://git.devuan.org/Daemonratte/gtk2-ng is quite ok-ish, in my opinion. Granted, it is mostly copy/paste from github but that still is about 1000000x better than sourceforge's interface - and gitlab's UI too (I just hate gitlab's UI, they seem to love complexity and a billion features only 0.000001% ever need; Git…

Github definitely has the better UI but if it weren't for network effects I'd be pushing to migrate to Gitlab pretty hard.
Post reply on HN