[flagged]
Incident with Pull Requests, Issues, Git Operations and API Requests
211–220 of 221 posts
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#212Earlier quoted context omitted.
> Who cares how it was produced? Well, we're at least two people who care, since we were conversing about how good/bad the webdesign is, then you jumped in here :) If you don't care, why bother to reply to people who seemingly do care? What kind of conversation are you expecting here, "Yeah, do tooo"? :|
Could you explain why you care?
Why I care about understanding people who think differently than me? I don't know, always did, not sure exactly why, always been interesting to understand people's perspectives, especially when I personally feel differently, tends to help myself understand me better too, so it's basically a win-win to get people to explain their reasoning.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#213Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#214Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#215Earlier quoted context omitted.
It's not physically possible to run post-mortems for issues at those rates. They should install OpenClaw for that as well.
> It's not physically possible to run post-mortems for issues at those rates. Not at all, you merely move the goal post of at what layer the "root cause" actually could come from! At that speed, it's always something short and sweet, while when you actually want to long-term address things, you have to have time to even investigate organizational issues or whatever the actual problems stem from. But you have half a d…
“A failure occurred. This was caused by something going wrong. Changes to operating guidelines have been instituted to ensure that things will not go wrong in the future unless we happen to do the same thing again.”
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#216Earlier quoted context omitted.
Yea but thats not really an excuse, is it? They offer a service, (some) people pay for that service and should therefore expect it to work. If GitHub cannot keep up with the growth then they could disable new account registrations or start reducing free tiers so people either use the free tier more mindfully or need to pay for usage-base products like Actions which would GitHub allow to scale.
I mean it's an easy problem to solve when it's just speculating solutions. But there's a very possible reality where in 5 years guys are making YouTube video essays about the fall of Github caused by their "obviously stupid decision" to throttle access to people who were trying to use their service in record numbers, leaving opportunity for someone else to come in and take their lunch. I don't envy their position of…
It’s not quite as cacheable as YouTube, but a lot of it is still pretty cacheable. Actions aren’t. Issues, wikis, and READMEs are. File views are. Most projects aren’t changing daily. The few that change daily aren’t changing hourly. There are a few that change constantly and would require constant cache updates. But the long tail is pretty static.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#217[flagged]
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#218Earlier quoted context omitted.
I’m actively working on an alternative Frontend for Forgejo at the moment, completely self hostable, free, and open source. Moving everything from GitHub to Forgejo and Tangled for now. These outages haven’t effected me for the past month because of this.
Can you elaborate on how your Forgejo frontend will be different than the default one? I'm asking because I've only ever used GitHub, GitLab and Forgejo for longer periods and Forgejo was the fastest and easiest to use for me.
It’s still early days, but I already have it in a useable state so I could share more such as early screencaps.
I plan on focusing primarily on these areas:
- mobile experience is first class, even on old/slow devices
- diff viewer is fast even on extremely large pull requests
- stacked pull request support
- user interface is modern, accessible, and theme-able with a light touch of whimsy
- search is accessible from anywhere
- opinionated keyboard shortcuts and commandk palette from day one
Many other longer term goals that I’m not mentioning here for now while the roadmap is forming.
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#219Earlier quoted context omitted.
Wow, it seems that 100% of sev-3 ("critical") incidents in the last year (=365 days) have occurred between April 22, 2026 and now. Is it possible that there has been a change in the way the data are collected/recorded that even partially accounts for this sudden onset?
One tangent, I believe sev-0 is actually "critical" (at least as how I'm used to reading it), and the higher you go the less critical something is. IMO as a github-watcher, I think they changed their definition of what constitutes a sev-0 between sev-1 for the better. In particular, they had a few "sev-1"'s around the turn of the year that would be classified as sev-0's if they happened today. Pre-4/22 GitHub sev-1 w…
Ah, thank you for the correction on sev-0.
To be clear, your observation that "they changed their definition of what constitutes a sev-0" is based just on your external observation of incidents and their designations, correct? I.e. they haven't officially released a statement saying they have changed their standards
Re: Incident with Pull Requests, Issues, Git Operations and API Requests
#220Earlier quoted context omitted.
Forgejo is fantastic. I do think it could use a fresh coat of paint from a designer but it’s otherwise really good. Gitea (what Forgejo forked from) recently stole the sidebar on repos from GitHub and I think that would be great for Forgejo to steal too… Forgejo themed by Codeberg: https://codeberg.org/forgejo/forgejo (the codeberg theme is extremely low contrast) Forgejo default: https://v15.next.forgejo.org/pparaxa…
That Blender Gitea theme is really nice! I wonder why exactly it's so much easier on the eyes? In a lot of ways all of these are "just Github" with minor changes, so the one that is actually better really stands out.
I like it too, is it available for download anywhere?