search

rust-lang / crates.io

The Rust package registry
https://crates.io
Apache License 2.0
2.96k stars 600 forks source link

Bad gateway error when wanting to remove access for a team #1205

Open est31 opened 6 years ago

est31 commented 6 years ago

I was trying to remove access for a team, then I got an error:

$ cargo owner --remove github:rustaudio:owners
    Updating registry `https://github.com/rust-lang/crates.io-index`
       Owner removing ["github:rustaudio:owners"] from crate deepspeech-sys
error: failed to remove owners from crate deepspeech-sys: failed to get a 200 OK response, got 502
headers:
    HTTP/1.1 100 Continue

    HTTP/1.1 502 Bad Gateway

    Connection: keep-alive

    Server: nginx

    Date: Fri, 15 Dec 2017 04:48:51 GMT

    Content-Type: text/html

    Content-Length: 166

    Strict-Transport-Security: max-age=31536000

    Via: 1.1 vegur

body:
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

I'm both member of the team as well as owner of the crate.

carols10cents commented 6 years ago

Strange. Because this is coming from nginx, I don't think the request is even getting to crates.io's logic around teams/members/owners.

I'm not able to reproduce. I see several 502s in the logs for deepspeech and deepspeeech-sys around when you posted this issue. I'm suspecting a transient network error, are you still able to reproduce consistently?

est31 commented 6 years ago

@carols10cents I was changing the team name from owners to cratesio-push and adding the cratesio-push team worked, but removing the owners team gave an error. Just now I've tried again and I'm still able to reproduce, so the error is consistent.

est31 commented 6 years ago

It seems the issue is not concentrated to removing access. Apparently yanking is affected as well! @centril just tried to yank something and got a 502 Bad Gateway too. The cratename is proptest-quickcheck-interop if you want to troubleshoot it in the logs.

Centril commented 6 years ago

Yup, I got:

D:\programming\proptest\proptest-quickcheck-interop (master)
λ cargo yank --vers 1.0.0
    Updating registry `https://github.com/rust-lang/crates.io-index`
        Yank proptest-quickcheck-interop:1.0.0
error: failed to yank: failed to get a 200 OK response, got 502
headers:
    HTTP/1.1 502 Bad Gateway

    Connection: keep-alive

    Server: nginx

    Date: Sat, 16 Dec 2017 20:44:44 GMT

    Content-Type: text/html

    Content-Length: 166

    Strict-Transport-Security: max-age=31536000

    Via: 1.1 vegur

body:
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>