Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to install swaggo@latest #1561

Closed
dud225 opened this issue Apr 18, 2023 · 7 comments · Fixed by #1562
Closed

Unable to install swaggo@latest #1561

dud225 opened this issue Apr 18, 2023 · 7 comments · Fixed by #1562
Assignees

Comments

@dud225
Copy link

dud225 commented Apr 18, 2023

Hello

Since a few hours installing swaggo@latest fails:

$ go install -x github.com/swaggo/swag/cmd/swag@latest
# get https://proxy.golang.org/github.com/@v/list
# get https://proxy.golang.org/github.com/swaggo/swag/@v/list
# get https://proxy.golang.org/github.com/swaggo/swag/cmd/swag/@v/list
# get https://proxy.golang.org/github.com/swaggo/swag/cmd/@v/list
# get https://proxy.golang.org/github.com/swaggo/@v/list
# get https://proxy.golang.org/github.com/@v/list: 404 Not Found (0.063s)
# get https://proxy.golang.org/github.com/swaggo/swag/cmd/swag/@v/list: 404 Not Found (0.074s)
# get https://proxy.golang.org/github.com/swaggo/@v/list: 404 Not Found (0.094s)
# get https://proxy.golang.org/github.com/swaggo/swag/cmd/@v/list: 404 Not Found (0.098s)
# get https://proxy.golang.org/github.com/swaggo/swag/@v/list: 200 OK (0.099s)
go: github.com/swaggo/swag/cmd/swag@latest: github.com/swaggo/swag@v1.16.0: parsing go.mod:
        module declares its path as: github.com/Nerzal/swag
                but was required as: github.com/swaggo/swag

It looks like Nerzal/swag has been published as swaggo/swag:

$ curl https://proxy.golang.org/github.com/swaggo/swag/@v/list 
v1.9.0
v1.7.0
v1.8.8
v1.8.12
v1.7.9
v1.8.9-rc1
v1.6.8
v1.5.1
v1.8.0
v1.6.4
v1.6.5
v1.7.8
v1.6.0
v1.0.0
v1.8.10
v1.6.9
v1.8.3
v1.8.11
v1.8.5
v1.8.7
v1.8.9
v1.8.2
v1.8.9-rc2
v1.1.1
v1.8.6
v1.5.0
v1.7.2
v1.7.1
v1.4.1
v1.6.3
v1.7.3
v1.8.9-rc3
v1.7.5
v1.3.2
v1.4.0
v1.6.1
v1.7.7
v1.7.9-p1
v1.6.6
v1.8.1
v1.6.2
v1.7.4
v1.16.0
v1.0.1
v1.1.0
v1.8.4
v1.6.7
v1.7.6

I can assert that it was working fine 20h ago.

@webgoCoding
Copy link

Hi, confirming the issue also appears here.

@Nerzal Nerzal self-assigned this Apr 18, 2023
@Nerzal
Copy link
Contributor

Nerzal commented Apr 18, 2023

The wrongfully pushed tags are now deleted.
I guess the proxy (proxy.golang.org) has some sort of cache, that leads to it still serving the tags?

@Nerzal
Copy link
Contributor

Nerzal commented Apr 18, 2023

Looks like removing the tags is not enough, and a retract statement needs to be added

@hutaochu
Copy link

I have same issue

@Nerzal
Copy link
Contributor

Nerzal commented Apr 18, 2023

Until the retract directive is merged, you could use:

For stable version:

go install -x github.com/swaggo/swag/cmd/swag@v1.8.12

@Nerzal
Copy link
Contributor

Nerzal commented Apr 18, 2023

Another workarround, until the retract directive is merged is to ignore the proxy.

Example:

GOPROXY=direct go install -x github.com/swaggo/swag/cmd/swag@latest

@Nerzal
Copy link
Contributor

Nerzal commented Apr 18, 2023

Problem solved by publishing a new tag, that points to current master branch commit.
The linked PR is going to cleanup the cached tag in the proxy

@Nerzal Nerzal closed this as completed Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants