Crate succeeds to build, but some pages are unreachable

rust-lang / docs.rs

crates.io documentation generator

https://docs.rs

MIT License

956 stars 193 forks source link

Crate succeeds to build, but some pages are unreachable #2536

Open Bromeon opened 6 days ago

Bromeon commented 6 days ago

Crate name

godot

Build failure link

https://docs.rs/crate/godot/0.1.1/builds

Additional details

Several modules in the godot crate page are unreachable. Some like builtin work, others like classes don't. https://docs.rs/godot/0.1.1/godot/#modules

The error message is: The requested resource does not exist

In case this is a misconfiguration on my side, could you help me point that out? See also downstream issue https://github.com/godot-rust/gdext/issues/779.

Thanks a lot in advance! :slightly_smiling_face:

syphar commented 6 days ago

This odd, but I have a hunch what the reason could be.

I'm currently on the way back from rustfest zürich, with wonky internet connection, will look into it later today

syphar commented 6 days ago

Still odd, I checked the two typical issues / solutions for these kind of errors, both didn't help.

I need to dig deeper and see if I can reproduce this locally to debug

StatisMike commented 5 days ago

At least currently, all pages seem to be showing up on when choosing every platform besides x86_62-unknown-linux-gnu (which is default)

syphar commented 5 days ago

note to myself, things I just checked:

normal cargo doc locally looks good
the archive of the built docs ( https://docs.rs/crate/godot/latest/download ) looks complete for all targets

next step:

run the build locally, so I can see if the issue is in the webserver, or the archive index file

syphar commented 2 days ago

now it gets tricky: local build succeeds, and all pages I tested worked.

in the logs on the server I saw an odd "missing bz2 header", though I couldn't directly link it to this crate.

Next test I'll do is to download the archive index & archive from S3, and test locally with these. Also I'll probably have to extend logging in the respective handler.