Skip to content

Veto ML output when rules have no false negatives - #1529

Closed
ia0 wants to merge 1 commit into
google:mainfrom
ia0:veto
Closed

ia0 wants to merge 1 commit into
google:mainfrom
ia0:veto

Conversation

@ia0

@ia0 ia0 commented Oct 7, 2026

Copy link
Copy Markdown
Member

This also adds support for ZIP (otherwise rules would veto ZIP without reading the tail).

This doesn't add "debugging" information to FileType yet. This will be done later. This PR is about functionality only (not final API).

@ia0

ia0 commented Oct 9, 2026

Copy link
Copy Markdown
Member Author

Closing in favor of #1530 which contains this change.

@ia0 ia0 closed this Oct 9, 2026
@ia0
ia0 deleted the veto branch October 9, 2026 14:33
ebursztein added a commit that referenced this pull request Oct 9, 2026
The GPU qualification test only compiles on macOS or with CUDA, so CI did not see that it still used Features.0 and the old FileType::convert signature. It now passes the options, with rules off since the reference outputs are the model's alone, and maps RulesVeto as unreachable.
ebursztein added a commit that referenced this pull request Oct 9, 2026
Features extracted with use_rules = false recorded an empty list of matching rules, so a session with rules on vetoed every prediction whose rules have no false negatives: real WAV, PSD, Parquet and XLSX files came out unknown. Features now record None when the rules did not run, and the veto needs evidence that they ran and did not match.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant