Fix regressions in coding style PR#38
Merged
tvdijen merged 1 commit intoJul 8, 2026
Merged
Conversation
Member
|
My apologies! Tagged v1.4.1 |
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 code style PR introduced four separate bugs, fortunately all in error logging. I tripped over this whilst getting an error message that didn't make sense, and tracked it to parameters in the logging being wrong (the first change below). I subsequently found another three changes in that PR that would put out wrong logging output.
Assuming this is approved and merged, could you please mark another release after merging?