As of CL 360442 (CC @julieqiu, @dmitshur), golang.org/x/build/repos lists the "vuln" repository as shown on the dashboard, but build.golang.org is serving 502s for that repository:
~/src/golang.org/x/build$ curl -i 'https://build.golang.org/?mode=json&page=0&repo=golang.org%2Fx%2Fvuln'
HTTP/2 502
content-type: text/html; charset=UTF-8
referrer-policy: no-referrer
content-length: 332
date: Wed, 03 Nov 2021 14:03:23 GMT
alt-svc: clear
<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
This state is problematic for tools that use the repos package to identify which repos to fetch from the dashboard, such as cmd/fetchlogs in CL 360354.
(This might be resolvable by redeploying cmd/coordinator; I'm not sure.)
The text was updated successfully, but these errors were encountered:
bcmills
added
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
and removed
Builders
x/build issues (builders, bots, dashboards)
labels
Nov 3, 2021
This is indeed a matter of redeploying cmd/coordinator. I've held off on doing that, but will do after a minor release. Sorry for the temporary trouble for fetchlogs.
dmitshur
added
NeedsFix
The path to resolution is known, but the work has not been done.
Soon
This needs to be done soon. (regressions, serious bugs, outages)
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Nov 3, 2021
As of CL 360442 (CC @julieqiu, @dmitshur),
golang.org/x/build/repos
lists the"vuln"
repository as shown on the dashboard, butbuild.golang.org
is serving 502s for that repository:This state is problematic for tools that use the
repos
package to identify which repos to fetch from the dashboard, such ascmd/fetchlogs
in CL 360354.(This might be resolvable by redeploying cmd/coordinator; I'm not sure.)
The text was updated successfully, but these errors were encountered: