Change log level from fine to info for unknown fields - #105
Merged
Conversation
This was already a suggested change in zarr-developers#75 It was my mistake to advise you to revert it back to fine. It would be better, if it was info instead. Sorry, I was mixing up the meaning of FINE and DEBUG/TRACE and thought FINE would stand for lower severity, but in fact it stands for higher severity, which we do not want for this case.
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.
This was already a suggested change in #75
It was my mistake to advise to revert it back to FINE. It would be better, if it was INFO instead. Sorry, I was mixing up the meaning of FINE and DEBUG/TRACE and thought FINE would stand for lower severity, but in fact it stands for higher severity, which we do not want for this case.