Skip to content

Allow Bad Vins#223

Open
zer0stars wants to merge 2 commits intomainfrom
feature/allow_bad_fingerprint
Open

Allow Bad Vins#223
zer0stars wants to merge 2 commits intomainfrom
feature/allow_bad_fingerprint

Conversation

@zer0stars
Copy link
Copy Markdown
Member

Description
This PR updates the fingerprint validation logic to be more tolerant of invalid VINs during device startup. Previously, if a fingerprint event contained an invalid VIN, the processor would set an error on the message. Now, if an invalid VIN is detected (and it is not a valid Japan Chassis), the processor will simply log a warning and continue processing without marking the message as an error.

Motivation
Some devices may send invalid fingerprints when starting up, which is expected and should not be treated as an error. This change prevents unnecessary error reporting for these cases, improving robustness and reducing noise in logs and monitoring.

Changes
Updated the fingerprint validation processor to:
Log a warning instead of setting an error when an invalid VIN is encountered during device startup.
Continue processing the message batch as normal.
Impact
Reduces false-positive error reporting for fingerprint events with invalid VINs during device startup.
No impact on valid VIN processing or other event types.
Testing
Existing tests for valid and invalid VINs remain in place.
The processor now logs a warning for invalid VINs instead of erroring.

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