go-import metadata is broken
Summary
Go-import metadata generated by gitlab is broken. It was fine last week, so something deployed this week must have broken it. I am seeing this on gitlab.com
$ curl 'https://gitlab.com/f21/some-repo?go-get=1'
<html><head><meta name="go-import" content="gitlab.com/f21/some-repo git " /></head></htm>
Correct metadata should be in this format:
<html><head><meta name="go-import" content="gitlab.com/f21/some-repo git https://gitlab.com/f21/some-repo.git" /></head></htm>
It seems to be introduced with the deployment of 10.2.0 RC2 around 8 hours ago.
This is prevent us from using go get
or dep
to fetch dependencies from our gitlab repos, which is blocking us.
Steps to reproduce
GET https://gitlab.com/f21/some-repo?go-get=1
using your favorite HTTP client.
Example Project
N/A
What is the current bug behavior?
Returns broken metadata: <meta name="go-import" content="gitlab.com/f21/some-repo git " />
(missing git repo clone path)
What is the expected correct behavior?
Should return correct metadata: <meta name="go-import" content="gitlab.com/f21/some-repo git https://gitlab.com/f21/some-repo.git" />
.
Relevant logs and/or screenshots
N/A
Output of checks
This bug happens on GitLab.com
Possible fixes
N/A
/label ~bug