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...
Sad times ahead.
Incident with Actions and Pages
321–330 of 407 posts
Re: Incident with Actions and Pages
#322As 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?
Running tests locally. It's primitive, but incredibly reliable, and a breeze to debug if (big if) there is any dependency issue.
Re: Incident with Actions and Pages
#323I recently switched from GitHub Actions to Buildkite + self-hosted runners.
Setting it all up would have been tediously annoying eight months ago (Buildkite requires setting up GitHub webhooks for each repo).
Last week I just had codex set up everything, ephemeral vm runners and all, using a couple of low-spec refurb mac minis, Buildkite’s API, a short-lived API token, and migrate my repositories one by one.
So far so good, it’ll pay for itself within two to three months, and following today’s outage I suggested at work that we experiment with the same set up.
They’re considering it.
Re: Incident with Actions and Pages
#324CircleCI right now https://gifrific.com/mick-mccarthy-stares-at-camera-and-smil...
Re: Incident with Actions and Pages
#325My action failed with "Unexpected error fetching GitHub release for tag refs/heads/master: HttpError: Sorry. Your account was suspended" Which certainly made me shit myself, briefly.
It's an eye opener. Think about it - today, it was a mistake. But, what if it really happened? What if you really lost access to all your years of hard work? It's a wake up call. A blessing in disguise to store what matters to you the most locally, backed up offline. Never trust any single provider. Be it MS or Google or Apple. RAID is the way.
Well yes, my git repositories sit on my laptop, that's the entire point. If github banned my country because its president has a tis, I can push my entire commit history to another company. Same with anyone else who's working on it.
It would be a pain as I'd have to set up a few integrations again, but github is far lower down the risk scale than the vast majority of SAAS providers
Re: Incident with Actions and Pages
#326Earlier quoted context omitted.
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.
Gitlab’s UI is extremely terrible. It’s hard to even explain how bad it is.
Re: Incident with Actions and Pages
#327Aws made a very big mistake to stop their CodeCommit service. They could have eaten Githubs lunch if they had continued to build it out
Re: Incident with Actions and Pages
#328Earlier quoted context omitted.
Ah, yes, I misunderstood. And I have seen cases where a direct CPU alert makes sense, but 99 times out of 100 times I see it, it's nothing but trouble. Worse, I tend to see the cpu alert when there are no end to end synthetic alerts, 500 alerts, queue depth alerts, etc. If your requests are fast and cheap, you can probe frequently relative to your goals, but often that's not really possible (think, long SQL queries,…
Yeah very true. Talking about long SQL queries, I quite like throwing CPU alerts on database servers. They'll be a low priority alert (ie no out of hours "pagers") so just something that goes into a slack channel. But they're a good indicator of when developers have poorly optimized SQL, or the DB schema is poorly defined (eg missing indexes), or the DB server itself is poorly sized. This wouldn't be something you'd…
Oh, I was thinking about it as the person running SQL as a service. People run queries that go on for days....
idle CPU is often wasted CPU
Re: Incident with Actions and Pages
#329Earlier quoted context omitted.
It's an eye opener. Think about it - today, it was a mistake. But, what if it really happened? What if you really lost access to all your years of hard work? It's a wake up call. A blessing in disguise to store what matters to you the most locally, backed up offline. Never trust any single provider. Be it MS or Google or Apple. RAID is the way.
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.
> Some sort of 'distributed source control system' maybe
The day it broke away and became centralized was when we had a PR + mandatory "Required actions" to merge to main.
Re: Incident with Actions and Pages
#330At this point, GitHub should rename itself downhub.