I like how "Every request returns a 404" == "degraded performance"
It should load faster if there's nothing to load
We are investigating reports of degraded performance
31–40 of 152 posts
Re: We are investigating reports of degraded performance
#32Re: We are investigating reports of degraded performance
#33Re: We are investigating reports of degraded performance
#34Re: We are investigating reports of degraded performance
#35Earlier quoted context omitted.
In theory, the code is there, but putting a project back together in a hurry after trouble at Github is non-trivial. Especially if the build process uses proprietary stuff such as "GitHub actions". The issues and discussions are all Github-only, too.
It’s crazy that there is no common CI spec. Every single platform is completely different. Last time I tried Act it had some pretty severe limitations. Perhaps I should take it for another spin.
Git hook management's really awkward. Even with tools to synchronize them (... all of them? You may want some that are just for your own use) it's a pain. "I want these hooks to run, in order, but only when a merge commit happens on a machine with such-and-such designation, and I want it to run the task on a different machine, but we need to make sure that runner's a Windows box because..." that just sucks to self-manage, and yeah, there's no standard for expressing that, you're bound to incompatible solutions.
Secret management's a hellscape and everyone's always glad when someone else solves the problem for you. That alone is like 50% of the value of Github Actions.
Re: We are investigating reports of degraded performance
#36PR really spun gold when they decided to label everything from every single one of their databases getting deleted and backups nuked to intermittent connectivity issues as "degraded". Who exactly are they making feel better by not calling a spade a spade?
Re: We are investigating reports of degraded performance
#37Earlier quoted context omitted.
If only there was a decentralized system to allow version management of code.
Sadly, GitHub doesn't store its value-add assets within the repository itself; so all of the PR conversations, Gists, Issues, and so forth aren't within git itself.
Re: We are investigating reports of degraded performance
#38Seriously people: gitea exists. Gitlab self-hosted exists. Drone/Woodpecker CI exists. It's not that difficult to set up a project that does not depend on Github. I spent less time setting these up than the amount of down time that Github has had this year.
Re: We are investigating reports of degraded performance
#39PR really spun gold when they decided to label everything from every single one of their databases getting deleted and backups nuked to intermittent connectivity issues as "degraded". Who exactly are they making feel better by not calling a spade a spade?
Re: We are investigating reports of degraded performance
#40Github is becoming too important. A routine backup system is needed, something like archive.org, that backs up important Github projects.
Host a backup of your own code? It’s easy and can be done on a rpi. I wrote a go program in 1000 lines that automatically does this for me. And then I actually started using that as the main source and pushing the backup to github. It also pulls down anything i star into a different folder which get a sync one a day. The rest get a sync every hour.