Skip to content

docs.rs/cratename redirect to version with failed build gives "The requested resource does not exist" and no links #232

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

Closed
huonw opened this issue Sep 3, 2018 · 2 comments · Fixed by #325

Comments

@huonw
Copy link
Member

huonw commented Sep 3, 2018

The short-links like https://docs.rs/im seem to do a redirect to the latest published version of the crate (which is 12.0.0 for that crate at the time of filing, i.e. https://docs.rs/im/12.0.0/im/). If that version failed to build, then the page is rather useless: just "The requested resource does not exist". It would be nice to give more information, such as a link to the crate page (e.g. https://docs.rs/crate/im/12.0.0) which at least has info about build failures, and/or a link to the latest successful build.

(A more general form of this issue is arbitrary URLs that are invalid but still "obviously" referring to a specific crate, e.g. https://docs.rs/crate/im/100.0.0. These could also contain a link back to the crate they refer to.)

@dpc
Copy link

dpc commented Sep 18, 2018

This is really bad user experience. Many of places all over the web have links like https://docs.rs/mycrate and then the "The requested resource does not exist" it's a big WAT for the user. There are not even any pointers how to find last version that did work.

@eddyb
Copy link
Member

eddyb commented Oct 19, 2018

I stumbled onto this and discussed it with @QuietMisdreavus - I would prefer a redirect from a version that failed to build, to the crate/ page.
For the versionless link, I think it's fine for it to go to the last-known-good version, and the "go to the latest version" link would trigger the aforementioned redirect.

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.

3 participants