Contingency action plan: Codeberg. Engage.
Incident with Actions and Pages
121–130 of 407 posts
Re: Incident with Actions and Pages
#122Yeah I'm getting an error where it says account has been suspended. They really are becoming an embarassment
this has happened to me too. i am guessing then it is not a real reason?
`github-actions[bot]` was disabled for some time, if that's the actor which does the checkout in your setup it could be related. FWIW it's back to working now.
Re: Incident with Actions and Pages
#123Earlier quoted context omitted.
GitHub had a blog post about this recently. They reported a significant uptick in volume (repos created, PRs, etc.), which they attribute to AI usage and tooling.
Do you really believe their competition hasn’t seen the same increase? Because their competition certainly hasn’t seen the same instability issues.
Yes, I truly believe that GitHub is recommended by an LLM orders of magnitude more frequently than any other forge
Re: Incident with Actions and Pages
#124Re: Incident with Actions and Pages
#125No way - everyone tells me the AI adoption is going great?
Re: Incident with Actions and Pages
#126Earlier 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
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've been oncall for a different G service that nearly paged on every error. It used the standard error budget tooling, but on hundreds of user buckets because the engineering around locality-specific configuration was... suspect. Many of these buckets had single-digits user. If a user was on their phone and lost signal, I was paged. Very poor oncall experience.
Re: Incident with Actions and Pages
#127Wasn’t my fault this time! I haven’t started work yet. https://news.ycombinator.com/item?id=47237377
Uh oh. That means there's at least one more like you out there that we don't know about.
I always wanted superpowers, but I never dreamed it'd be like this.
- So many super-heroes/super-villains
Re: Incident with Actions and Pages
#128Whilst 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…
What I don’t get about this is how you run OS specific tasks (Windows, macOS, Linux).. I started playing with proxmox VMs and containers in them (docker and tart) to see if I can build some local infrastructure to properly solve this…
We support macOS via tartlet, but basically it's always linux. If you need windows then it's gonna be an issue.
The jobs runs via containers.
Re: Incident with Actions and Pages
#129Tell Claude to fix it, simple.
Re: Incident with Actions and Pages
#130Why do they go down so often? Is it true that the reason is that they've incorporated too much AI without human review?
I personally trigger github actions approximately 50x more than I did prior to AI-driven developer coding and I'm not alone.
Totally agree. There's days (or even afternoons) where I trigger more actions than I would have done in a month.