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

Incident with Actions and Pages

githubstatus.com

Post reply on HN
Print view View original

211–220 of 407 posts

Re: Incident with Actions and Pages

#211

Post by bob1029 »

The last two projects I built I did the CI/CD manually with a small win32 service that polls git and builds+deploys the main service locally. It's barely 200 lines of code. Not much to go wrong. "dotnet publish" is not difficult to wrap.

The latest language models have enabled this sort of thing for me. I can integrate a mini Jenkins into every project within a 5-10 minute prompting session. This sort of code isn't hard. It's just tedious, and the LLMs absolutely rock at boring repetitive stuff. Having a win32 service start up successfully on the very first try is something I haven't experienced until 2026.

Re: Incident with Actions and Pages

#213

Post by Groxx »

Xirdus wrote: post #76
ramon156 wrote: post #48

Earlier quoted context omitted.

"Its not like act, because we can add AI" Is what it boils down to. > codex "Fix this pipeline, use `act` to verify your changes"

I had extremely bad experience trying to setup act on my Macbook. If this is something that actually works (and doesn't steal my credentials), I'm willing to try it despite AI non-features.

Yea, I've had only barely-success on only a few projects with act. Usually due to steps/scripts that use github-internal APIs, but afaict far from always.

I like that it exists, but what a freaking mess that it's necessary and so difficult to do.

Re: Incident with Actions and Pages

#214

Post by sarchertech »

Gigachad wrote: post #170
sarchertech wrote: post #77

Earlier quoted context omitted.

Yeah, it’s not even consistent with their own incident history. I spot checked it and consistently found incidents with downtime/elevated error rates in months listed as 100.00000% uptime on that chart.

The unofficial and offical charts are both lying. The GitHub one ignores actual outages and the unofficial ones count minor display bugs in minor features as a “github outage”.

The unofficial one has done that for years though so it’s useful for comparison. If you go back a few years it was regularly at 99.9% uptime.

Re: Incident with Actions and Pages

#216

Post by wasmitnetzen »

compumike wrote: post #202
echelon wrote: post #83

Earlier quoted context omitted.

In a high performance service with good maintenance and upkeep, you page for all 500s. A noisy pager forces the team to fix the 500s. Maybe the Github Actions infrastructure isn't run like that. edit: my oncall rotation notified on all 500s, 24/7, not just rates - https://news.ycombinator.com/item?id=48279262

Re: "page for all 500s": there's a world of difference between "page me with a critical alert at 3am" and "notify me on Monday morning when my normal workday starts". At the extremes: If my DB health check endpoint is returning 500s for N consecutive checks over M minutes, yeah, please wake me up at 3am! If one user hit a weird edge case in form validation and got a one-off 500, please don't! We can fix that on Monda…

Shouldn't Github be large enough to not have anyone on-call, but just rotate the responsible team around the world?

Re: Incident with Actions and Pages

#217

Post by anon7000 »

voxic11 wrote: post #185
ketzu wrote: post #33

Earlier quoted context omitted.

If the job queue is down, that wouldn't help, would it? On my repo the jobs do not get scheduled on the PRs at all, so I assume that separation wouldn't help for todays issue.

They have the github enterprise domain separated out and its working fine right now https://us.githubstatus.com/posts/dashboard

I’m not convinced they actually do, because GHE on the cloud tends to have the same problems as the main outages. Probably costs extra to be “single tenant” or whatever

Re: Incident with Actions and Pages

#219

Post by logifail »

jaapz wrote: post #62
drcongo wrote: post #55

Earlier quoted context omitted.

Same. It's weird how I always find out that GitHub is down before GitHub does. Took 15 minutes before it appeared on githubstatus.com

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.

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

Is it true that official service status pages are updated automatically?

Re: Incident with Actions and Pages

#220

Post by zombot »

JsonDemWitOster wrote: post #137
cpfohl wrote: post #11

Wasn’t my fault this time! I haven’t started work yet. https://news.ycombinator.com/item?id=47237377

Sorry guys it might be me. I vibe coded a script that interacts with both Gitlab and Github via their APIs and I've been using it pretty heavily since this morning. I crossed the streams! Goodness, I didn't know it would be _this_ bad!

It's only natural that this kind of promiscuity provoked an allergic reaction from Microslop.
Post reply on HN