Expected behavior
Expecting standard predicted output
Behavior observed
Instead of output, the following is printed:
thread 'main' panicked at C:\Users\PaulPEW\.cargo\registry\src\index.crates.io-6f17d22bba15001f\clap_builder-4.4.7\src\parser\error.rs:32:9:
Mismatch between definition and access of `throttle`. Could not downcast to TypeId { t: 25882202575019293479932656973818029271 }, need to downcast to TypeId { t: 96503125482807615452342895184004937604 }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Turning on RUST_BACKTRACE=1 and in PowerShell, I get the following more complete output:
Desktop (please complete the following information):
OS: Windows 11
Version v0.16.2
Additional context:
It seems clear that the issue is being thrown by clap_builder-4.4.7, but it is unclear whether this is a bug in that crate, or whether the bug exists in how mlc implements usage of that crate.
It seems like this issue filed on clapper has some information in the thread about how to ameliorate the situation.
Describe the bug Usage of the
--throttle
(or-T
) option causes a panic and fatal crash.To Reproduce Steps to reproduce the behavior:
mlc
:Expected behavior Expecting standard predicted output
Behavior observed Instead of output, the following is printed:
Turning on
RUST_BACKTRACE=1
and in PowerShell, I get the following more complete output:Desktop (please complete the following information):
v0.16.2
Additional context: It seems clear that the issue is being thrown by
clap_builder-4.4.7
, but it is unclear whether this is a bug in that crate, or whether the bug exists in howmlc
implements usage of that crate.It seems like this issue filed on clapper has some information in the thread about how to ameliorate the situation.