-
Notifications
You must be signed in to change notification settings - Fork 211
panic when releases.files is NULL #517
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
Comments
It looks like this happens whenever the build fails. |
I turned it into a 404 instead, at least we're giving an error message now. |
closes rust-lang#517 gives a 404 if you try to view the source
Reopening because of #521 |
While fixing this, I noticed that using the current master branch, binaries do not have their source code saved into the database. However, if I go to e.g. https://docs.rs/crate/bat/0.12.1/source/ all the code is there. Maybe the builder got changed at some point? If so I think it makes more sense to store the code in the DB even for binaries than to special case the error handling if it's not there (see also #520). cc @pietroalbini , could this have happened during the switch to rustwide? |
Not sure if I see the point of storing the source code for binaries... people shouldn't look on docs.rs for them. |
Ok, in that case I made a PR to fix the panic. |
Fixed in #526 |
Caught this from looking through the logs on the build server: https://docs.rs/crate/rips/0.2.0/source/ gives a 500 when you visit it. The build for
rips
failed, maybe that's why the files are NULL?Backtrace:
Note for maintainers: to find other crates with this issue, run this psql command on the server:
SELECT releases.target_name, releases.version FROM releases WHERE releases.files IS NULL;
The text was updated successfully, but these errors were encountered: