Remove redundant LFS logging information - #2479
Merged
Merged
Conversation
|
Build checks have not completed. Possible reasons for this are:
|
Member
Author
|
Build is passing, but compare base branch is failing (since main is broken right now) |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The LFS log events are unique and don't need line/file information
Since some of the LFS logs use 4 parameters, this was causing too many parameters of the maximum 6 to be used
I'm not sure why this wasn't a problem with GCC 10.3
To be honest I'm not a macro expert so I can't really debug the actual expansion, but I don't think we actually lose debugability here by dropping these