Enhance debugging: Improve logging for FURIOSA_METADATA_EXPECT_MODIFIED patterns #3
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.
This PR enhances the debugging information related to the FURIOSA_METADATA_EXPECT_MODIFIED setting. It provides clearer insights into whether a file is considered 'dirty' or 'pass' based on the configured patterns.
Key changes:
Motivation:
Previously, we had to rely on guesswork to determine if the patterns were functioning correctly. This lack of clear information made it difficult to debug and verify the behavior of the FURIOSA_METADATA_EXPECT_MODIFIED setting.
With these changes, we can:
This improvement will significantly enhance our ability to manage and debug metadata-related configurations, leading to more efficient development and troubleshooting processes.
LOG
ex)
export FURIOSA_METADATA_EXPECT_MODIFIED=".cargo/**:Cargo.*:crates/**/*.py:crates/**/CMakeLists.txt"
target/release/build/<package>-<hash>/stderr