178
Github confirms random 401 responses on unauthenticated git clones are no mistake (eviltoast.org)
submitted 4 days 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 4 days ago (1 child)

Wait, doesn't rust cargo pull from crates.io?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 4 days ago* (last edited 4 days ago) (2 children)

    crates.io pulls everything from github.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 15 points 4 days ago (1 child)

    No true at all.

    The index used to be from github but now it pulls from a CDN by default and doesn't do a full clone of the index. Crate downloads have always been pulled from a CDN.

    The index was quite small in the beginning this is why it worked.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 4 days ago (2 children)

    The service itself pulls from github to create the crates. Cargo pulls from crates.io, that is correct.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 9 points 4 days ago

    Who pulls from Github to create the crates? The crates are pushed by cargo publish to crates.io's API, not to github.

    crates.io does have an index in GitHub, but that's legacy and pretty much unused for reads now. GitHub doesn't store the crates themselves.

  • permalink
  • fedilink
  • source
  • parent