The source view is not available when crate failed to build.

[pftbest]

It should be possible to view the source code of a crate even if it failed to compile for some reason. I think some time ago this was working correctly, but I'm not sure.

It seems docs.rs is the only website on the internet which allows you to read the source code of a crate, because github link is often missing and even if it's not it contains a different source code than an actual crate version. It is very unfortunate that you are not able to see the source just because it failed to compile on docs.rs platform.

Example links:
https://docs.rs/crate/libui-sys/0.1.9/source/
https://docs.rs/crate/stm32ral/0.3.1/source/

[jyn514]

I think this should be as simple as moving this block outside of the if res.result.successful block:

docs.rs/src/docbuilder/rustwide_builder.rs

Line 331 in 5654923

debug!("adding sources into database");

[jyn514]

Testing instructions: Once you've gotten set up (either with docker-compose or natively), run a build for a crate that you know will fail to build. You can choose any crate off of https://docs.rs/releases/recent-failures.

# for docker-compose
docker-compose run web build crate <name> <version>
# running locally
cargo run build crate <name> <version>

You can then go to http://localhost:3000, click on the crate name, and click 'Source' in the top-left. It should show a list of all the files in the crate, including a Cargo.toml.

I expect this to also add sources for binaries when fixed, if you could test that as well that would be great, for example with bat 0.13.0.

[pftbest]

The same problem with binary crates. They all lost the source code too. Examples: cargo-bloat, ripgrep.

[jyn514]

This would be fixed by #826.

[pftbest]

Thank you!