Merged
Conversation
…display a warning with detailed information in debug
jeremylong
approved these changes
Mar 25, 2025
This file contains hidden or 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
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 of Change
The goal of this PR is to handle an unparsable toml file in case it does not respect the toml specification. As of now, the analysis fail in error when such a file is present.
This changes aims to provide a warning message telling the user the file could not be parsed and is therefore excluded from the analysis. The stack trace can be visible when debug logs are enabled.
Please note this PR also remove a copyright mention in both modified files, as advised by the Apache foundation.
Comments are welcomed!
Current behavior
Behavior introduced by this change
Related issues
Fixes #6819
Have test cases been added to cover the new functionality?
yes