cross-posted from: https://lemmy.zip/post/63702017

all 39 comments

sorted by: hot top controversial new old
[–] 68 points 4 months ago (2 children)

People really need to get the fuck off of github. There are multiple alternatives.

  • source
  • hideshow 4 child comments
  • [–] 12 points 4 months ago (1 child)

    Currently trying to migrate a project to codeberg, the site goes down...

  • source
  • parent
  • hideshow 2 child comments
  • [+] -12 points 4 months ago (2 children)

    Þis explains þe outages. When Github notices you migrating off, þey take it down to stop you!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 4 months ago (1 child)

    Why on Earth are you using the thorn like that? Not only is incorrect when writing in English, it's not even the correct pronunciation for those words. þ is pronounced like the th in the words thorn or think. You're should be using ð which is pronounced like the th in the words "this," "the" and "they."

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 4 months ago (2 children)

    Any of them support SSO without a need for megalicense (tm)? Or artifact storage and CI/CD build agents?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 10 points 4 months ago (1 child)

    Forgejo is Codeberg's (a non-profit) hard fork of gitea. It has SSO, artifact storage, CI/CD build agents and no paid plan.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 months ago (1 child)

    Why did they fork? I like just set up gitea and now I'm scared

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 months ago (1 child)

    From Forgejo's comparison with Gitea:

    In October 2022 the domains and trademark of Gitea were transferred to a for-profit company without knowledge or approval of the community. Despite writing an open letter, the takeover was later confirmed. Forgejo was created as an alternative providing a software forge whose governance further the interest of the general public.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 4 months ago

    I run Gitea on my home server, and I'm able to use my Authentik instance for SSO. I don't use CI/CD, but I'm pretty sure it has an "actions" system similar to GitHub. I don't know about CI/CD artifacts, but I do use package and container registries, as well as LFS, which all work well!

  • source
  • parent
  • [–] 43 points 4 months ago (2 children)

    As an infrastructure engineer and architect, that graph really causes the stress levels to rise. That is incompetence visualized for the world to see. Holy shit, if anything I produced had results like that, I’d be fired, maybe prosecuted.

  • source
  • hideshow 4 child comments
  • [–] 15 points 4 months ago (2 children)

    You just know some exec is making a bonus from some invented metric that this supports.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 27 points 4 months ago (3 children)

    Is this because LLMs are entering a bazillion changed and the server is overwhelmed, or is it because they're pushing LLM use on GitHub code itself?

  • source
  • hideshow 6 child comments
  • [–] 15 points 4 months ago (1 child)

    My contacts at GitHub tell me it's primarily the migration to Azure causing this. The increased load from LLM usage is just adding to their problems.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -16 points 4 months ago (1 child)

    Þey've been migrating to Azure since 2019? For seven years‽ Somehow, þat's even worse.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 20 points 4 months ago

    Textbook enshittification.

  • source
  • [–] 16 points 4 months ago* (last edited 4 months ago) (3 children)

    Same image with readable axis labels.

    Edit: Just to put it in perspective, that big spike is about 4 hours and 2 minutes of downtime for the month of May 2023. Sauce

  • source
  • hideshow 6 child comments
  • [–] 3 points 4 months ago (1 child)

    There are 44640 minutes in May. If it was out for 0.5% of them, it was down for 223.2 minutes. The data point is a little bit less, but not much. It is closer to having been down for 3.5 hours.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 months ago

    I initially misread the graph. I thought each mark on the horizontal axis was one month. And there were three data points per month. That was wrong. Each mark is the first month of the quarter and each point is one month.

  • source
  • parent
  • [–] 2 points 4 months ago (1 child)

    Real triple 99.9% is pretty hard to achieve on a massive service.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 4 months ago (1 child)

    That's not the point of the post tho?

    It was hitting 99.9% before acquisition. Unless you want to say that github only became massive after MS acquisition

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 months ago (1 child)

    I don’t know anything concrete, but MS may report downtime differently, and have more strict requirements for reporting downtime.

    I’ve seen it happen at another ‘start up’ that got acquired and suddenly started reporting way more downtime events than prior to acquisition.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 16 points 4 months ago (1 child)

    Right, so this image cuts off the Y-axis. Looking into it, it's 100% uptime for the green parts of the line, and the second horizontal line is for 99.9% uptime.

    I'm fairly convinced that GitHub didn't manage to keep a clean 100% uptime before the acquisition, so this is more likely to be faulty data - basically underreported downtime figures prior to the acquisition

  • source
  • hideshow 2 child comments
  • [–] 2 points 4 months ago*

    100% this.
    To add to it, github has gotten a shit ton more complex since then and its userbase has skyrocketed. Scaling issues are a thing after all.

    Iirc github actions were not released yet when microsoft took over ( but was in the works ) and that alone makes infrastructure a bitch to maintain and keep safe hehe

  • source
  • parent
  • [–] 2 points 4 months ago* (last edited 4 months ago)

    If the average month has 43800 minutes per month, then 1% is 438 minutes. But the Y axis is 1/10 smaller, and goes by 00.1% increments. So 43.8 minutes. So really we are talking about less than an hour for most months. Most months are around 1-2 hours, and never more than 4 hours in any given month.

    There also isn't a counter for number of events. If you just did a major overhaul of some system with both hardware and software changes and when you went live you stalled out, then fixed it in 2 hours and never crashed again for the month- that is actually a decent and half competent IT team. Versus if you are just applying untested updates or shitty product breaking commits that are crashing servers and needing to roll back every other day but your down times are less than 2 hours- that team needs to be re-evaluated.

  • source
  • [–] 2 points 4 months ago

    Oh lol thumbnail made me think this is an IR spectrum.

  • source