Recordscargoclapfailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-08 · Last seen: 2026-09-08
ArgAction::Append ArgAction::Count ArgAction::Set ArgAction::SetTrue ArgMatches::get_flag ArgMatches::get_one BoolishValueParser Command::build CommandFactory::command ErrorKind::ArgumentConflict ErrorKind::DisplayHelp ErrorKind::InvalidValue ErrorKind::MissingRequiredArgument ErrorKind::UnknownArgument ErrorKind::ValueValidation Parser::try_parse_from ValueEnum
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=rust · os=linux · runtime=rust@1 ×1 2026-09-08 → 2026-09-08
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 4.5.59 → first failing release 4.6.6
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No resolved dependency tree for 4.5.59 or for 4.6.6, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- clap 4.6.6: Resolve CLI arguments, environment variable fallbacks, boolish string parsing, and global flag propagation in clap 4 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWParser::try_parse_fromArgAction::SetTrueArgAction::SetBoolishValueParserArgMatches::get_flagArgMatches::get_oneErrorKind::InvalidValueErrorKind::ValueValidationErrorKind::UnknownArgumentrust MIT-0 · 2026-08-16
- clap 4.6.6: Handle Vec<T> single-value positional hijacking, comma delimiting, Option<Option<T>> optional values, and trailing vararg hyphen capture across clap 4 derive This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWParser::try_parse_fromArgAction::AppendArgAction::SetErrorKind::ArgumentConflictErrorKind::UnknownArgumentrust MIT-0 · 2026-08-16
- clap 4.6.6: Assert clap 4 builder API traps: downcast panics on get_flag/get_one type mismatches, get_many vs Vec downcast for Append, num_args(0..=1) requirement for default_missing_value, and argv[0] program name consumption in try_get_matches_from This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWclap::Command::try_get_matches_fromclap::Arg::default_missing_valueclap::Arg::num_argsclap::ArgAction::Appendclap::ArgAction::Countclap::ArgMatches::get_flagclap::ArgMatches::get_manyclap::ArgMatches::get_oneclap::ArgMatches::remove_onerust MIT-0 · 2026-08-16