feature: Adding proper logging to warn users when VEX data is not taken into account #2989
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…en into account Signed-off-by: syalioune <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adding proper logging to warn users when VEX data is not taken into account because either :
Addressed Issue
Fix #2977
Additional Details
N/A
Checklist
[] This PR fixes a defect, and I have provided tests to verify that the fix is effective[] This PR implements an enhancement, and I have provided tests to verify that it works as intended[] This PR introduces changes to the database model, and I have added corresponding update logic[] This PR introduces new or alters existing behavior, and I have updated the documentation accordingly