183
Github confirms random 401 responses on unauthenticated git clones are no mistake (eviltoast.org)
submitted 1 month ago by to c/programming@programming.dev
78 comments fedilink hide all child comments
 

Since yesterday a lot of users in Europe found their workflows failing due to Github seemingly randomly throwing HTTP/401 on git clone/git pull when interacting with public repos without authentication.

It was now confirmed by staff member that this indeed is intentional and no further steps are planned at this point.

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 month ago (2 children)

I believe that it is some fuckup and they don't know where exactly problem is and while they are looking for a way to fix it they've created plausible lie. When they'll fix it or believe that it's fixed there would be a public announcement like 'we heard the community and reversed our decision' and users will be happy. There is a serious need for github mirror, they are becoming less and less stable every year.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 13 points 1 month ago

    I'm 100% sure this is damage control on their part, they refused to acknowledge the incident and are looking for their way out.

    What users found in this thread is

    • problem is limited to EU
    • problem is limited to subset of git builds (gix version x TLS lib x TLS lib version in place)
    • problem goes away if you switch back to HTTP/1.1 for some reason

    If these are LLM scrapper mitigation steps then apparently fighting LLM scrappers is 7D chess game or something 🤷

  • permalink
  • fedilink
  • source
  • parent