• tal@lemmy.today
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    Thanks. Yeah, I’m pretty sure that that was what I was hitting. Hmm. Okay, that’s actually good — so it’s not a git bug, then, but something problematic in GitHub’s infrastructure.

    EDIT: On that bug, they say that they fixed it a couple months ago:

    This seems to have been fixed at some point during the last days leading up to today (2025-03-21), thanks in part to @MarinoJurisic 's tireless efforts to convince Github support to revisit this problem!!! 🎉

    So hopefully it’s dead even specifically for GitHub. Excellent. Man, that was obnoxious.

    • mesa@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      3 days ago

      I wonder if there is a retry or something on git? I know there is if you create a basic bash script, but we can assume someone is having the same issue, right?

      I did see some depth=1 or something like that to get only a certain depth of git commits but thats about it.

      I cant find the curl workaround I used a long time ago. It might have been just pulling the code as a zip or something like some GH repos let you do.

      • tal@lemmy.today
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 days ago

        I did see some depth=1 or something like that to get only a certain depth of git commits but thats about it.

        Yeah, that’s a shallow clone. That reduces what it pulls down, and I did try that (you most-likely want a bit more, probably to also ask to only pull down data from a single branch) but back when I was crashing into it, that wasn’t enough for the Cataclysm repo.

        It looks like it’s fixed as of early this year; I updated my comment above.