What could be the cause of GitHub issues from an engineering perspective?
Incident with Actions and Pages
171–180 of 407 posts
Re: Incident with Actions and Pages
#172I switched to GitLab a while ago and then spun it up locally.
Something’s wrong when my own infrastructure is more reliable than Microsoft’s.
Re: Incident with Actions and Pages
#173free service is down again, let's everyone that use the service for free complain again!!! (sorry for the sarcastic comment but i find it crazy how people feel they are entitled when it's free) EDIT: sorry i meant this rant at the one complaining for the free service not for the paid customers (which is unacceptable)
I was actually shocked when I saw what our org pays for Github, not cheap and defo not free
Re: Incident with Actions and Pages
#174Earlier quoted context omitted.
Do you know of a single service at a single company that actually does that? I know all of Gmail, every GCE service I can think of, every AWS service I can think of, Amazon.com, Netflix, and Github all do not page on just a single 500. I know none of those are particularly "high performance" though. Curious where your experience is coming from.
I worked at a large fintech moving billions of dollars in volume a day. I had a fairly long tenure, where I maintained multiple key services in critical online payments flow. Authentication, authorization, core business and risk data, as well as some cross-cutting control plane stuff, etc. You needed one or more of our services to take a payment, serve any request from the employee dashboard - pretty much everything…
> We paged for every single 500.
Assuming the existence of some kind of network (with zero guarantee of 100% reliability), how does this work in practice? Is each 500 treated as an event that needs investigation, even if the result of that would end up as 'a router dropped something from an internal buffer but the transaction as a whole was re-tried by a parent so the service itself recovered'?
Re: Incident with Actions and Pages
#175Earlier quoted context omitted.
Yes, Thais can be be really frustrating when you’re trying to get work done. There needs to be more competition and better alternatives and the LLMs need to offer easier connection to these alternatives.
What do the Thai people have to do with this? :(
Reminded me of the "Thai Fighter" joke from family guy's star wars spoof lol
Re: Incident with Actions and Pages
#176I moved a while back to Forgejo -> https://forgejo.org couldn't be happier. Highly recommended.
Looks good, but I'm not sure about security: https://bearyangry.com/2026/04/29/carrot-disclosure-forgejo-...
Looks lik a terrible source. Like someone ran Claude on the codebase, didn't analyse the results, then vibe coded a blog post. And the dustri.org link doesn't work for me
Anyway. Forgejo's response to it: https://floss.social/@forgejo/116494295922963052
Re: Incident with Actions and Pages
#177Whilst you're waiting for it to come back, try out AGENT-CI (which is a project I built.), which runs GitHub Actions on your machine: https://agent-ci.dev . (Open source, etc.) No, it's not like "act," because it uses the standard Github runner, the difference is that the control plane is an emulation of api.github.com, because of this we can do all kinds of nice things: Caching in ~0 ms. Pause on failure, so you can…
You're affiliated with the project. You should definitely be upfront about that when shilling.
You're right, figured it was implied, but now fixed.
Re: Incident with Actions and Pages
#178Earlier 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
that is absolutely not the case for any system of size and scale. that would just burn out the on-call team and not result in improvements. Error rates/budgets are used instead.
It depends what you're monitoring. If it's response codes from user generated queries, then I'd agree with you.
But if it is synthetic queries sent from the monitoring platform, then you control the user agent, payload, and endpoints. So any failed requests are a symptom of a misconfiguration and/or failure that should be investigated. Albeit not necessarily as a P1 priority.
Re: Incident with Actions and Pages
#179How to kill a business 101. The brand damage to business and owner is incalculable.
Re: Incident with Actions and Pages
#180Earlier quoted context omitted.
Yes, Thais can be be really frustrating when you’re trying to get work done. There needs to be more competition and better alternatives and the LLMs need to offer easier connection to these alternatives.
What do the Thai people have to do with this? :(
Pretty sure that they wanted to write "this", typed something different by accident, and auto-correct struck.