You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which seems to be entirely spurious. The output in #93428 and the dupe #93539 has
error: Unrecognized option: 'crate-version'
I think I am getting the complaint about default-theme instead of crate-version because I have that set in my rustdocflags in ~/.cargo/config. Both the complained-about options do exist, and everything works when rustdoc isn't panicking.
It seems that something must be wrong with the panic handling. It restarts argument processing somehow?
I checked a random ICE issue (93578) and it appears that rustc is not affected, or that the rustdoc "no entry found for key" panic is special, or something.
Not including a backtrace since there seem to be plenty of these about.
(NB this bug is not about the original panic; it is about the subsequent messages. So while #93428 is relevant since it provides a convenient repro, this bug is not the same as that one.)
The text was updated successfully, but these errors were encountered:
With a version of rustdoc affected by #93428, I observe this when this bug occurs:
Note the message
which seems to be entirely spurious. The output in #93428 and the dupe #93539 has
I think I am getting the complaint about
default-theme
instead ofcrate-version
because I have that set in myrustdocflags
in~/.cargo/config
. Both the complained-about options do exist, and everything works when rustdoc isn't panicking.It seems that something must be wrong with the panic handling. It restarts argument processing somehow?
I checked a random ICE issue (93578) and it appears that rustc is not affected, or that the rustdoc "no entry found for key" panic is special, or something.
Meta
Not including a backtrace since there seem to be plenty of these about.
(NB this bug is not about the original panic; it is about the subsequent messages. So while #93428 is relevant since it provides a convenient repro, this bug is not the same as that one.)
The text was updated successfully, but these errors were encountered: