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

go.dev: easy way to update packages #39336

Closed
aclements opened this issue Jun 1, 2020 · 2 comments
Closed

go.dev: easy way to update packages #39336

aclements opened this issue Jun 1, 2020 · 2 comments
Labels
Milestone

Comments

@aclements
Copy link
Member

@aclements aclements commented Jun 1, 2020

What is the URL of the page with the issue?

https://pkg.go.dev/github.com/aclements/go-misc/stress2

What is your user agent?

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36

Screenshot

image

What did you do?

I pushed a new package/module to github.com/aclements/go-misc/stress2.

What did you expect to see?

I expected pkg.go.dev to try fetching the module since it wasn't in its cache, or at least to provide an easy way to pull the latest version (a link or button).

What did you see instead?

A 404 page. It includes a link to instructions on how to add a package, but those instructions aren't easy to follow. The package I pushed is a "main" package, so it's not going to be imported by something else that would pull it into the cache. And since I haven't version tagged it, I have no idea how to form the appropriate proxy.golang.org request. Finally, if this was an existing package I had updated and I simply wanted to refresh the documentation, pkg.go.dev wouldn't even offer me the link to the instructions.

@gopherbot gopherbot added the pkgsite label Jun 1, 2020
@gopherbot gopherbot added this to the Unreleased milestone Jun 1, 2020
@aclements
Copy link
Member Author

@aclements aclements commented Jun 1, 2020

Fishing around some more, this appears to be related to #37106, #37002, and #36811. Feel free to close as a dup if you feel this bug doesn't add anything. Thanks!

@julieqiu
Copy link
Contributor

@julieqiu julieqiu commented Jun 8, 2020

Thanks for the added context, @aclements! Understanding your user journey is really helpful. Going to close this since we are already addressing this feature in the issues you linked, and will post updates there.

@julieqiu julieqiu closed this Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.