-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
error: could not document crate: the compiler unexpectedly panicked: Option::unwrap #113656
Comments
This is a new issue by the way. I cannot remember what version exactly, but previously I was using a version of around E.g. |
Bisection result: searched nightlies: from nightly-2023-07-09 to nightly-2023-07-13 bisected with cargo-bisect-rustc v0.6.6Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --regress=ice -- doc --all-features --no-deps cc @spastorino |
Is there something you or anyone need more from me on this one by the way? |
FYI, for now I pinned my toolchain to |
No, I'll take a look at this today and hopefully have a fix up soon. Thanks, @GlenDC. |
We're accessing hir for RPITITs in this case in ... // FIXME(@lcnr): Remove this function.
pub fn get_attrs_unchecked(self, did: DefId) -> &'tcx [ast::Attribute] {
if let Some(did) = did.as_local() {
self.hir().attrs(self.hir().local_def_id_to_hir_id(did))
} else {
self.item_attrs(did)
}
} Likely we want a check for |
This might also be the reason why docs are for now failing at https://docs.rs/crate/tower-async/latest ![]() |
This is the url to the build log btw: https://docs.rs/crate/tower-async/0.1.0/builds/863682 (you can also access it from the linked docs.rs crate doc page). Too bad I cannot select the toolchain with https://docs.rs/about/metadata that would fix it for that use case as well. |
Can I help with fixing this issue? If someone can mentor me I do not mind picking it up? |
Sorry, I'm working on it. I was experimenting with a bit more thorough fix, but that fell through the cracks since I was traveling the past few weeks. |
Ah yes, no worries. No pressure. In that case I’ll wait patiently. Do let me know if I can be of any more meaning now or later, as I’m pretty invested in these functionalities. |
This issue got fixed, right? I can't reproduce it (using plabayo/tower-async#bd868b123eeb4fc65ea066fb107e3e41c306b4b3 from your repo). |
Can the docs.rs version of https://docs.rs/crate/tower-async/0.1.1 be recompile for me? Or do I need to request that as a separate issue somewhere else @compiler-errors ? |
I'm not on the docs.rs team (only on the rustdoc-contributors team) and therefore don't know their procedures. However, after having read https://docs.rs/about/builds#failures-and-rebuilds it seems to me that you can request a rebuild after a bug in |
Thanks I have opened an issue in the right repo, rust-lang/docs.rs#2215. |
Code
plabayo/tower-async#3
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: