Fix newline JSON unmarshalling bug#177
Merged
Merged
Conversation
vivientran42
commented
May 11, 2026
angrykoala
requested changes
May 14, 2026
Member
angrykoala
left a comment
angrykoala
left a comment
There was a problem hiding this comment.
This should have a patch changelog entry (with changie)
You can follow the instructions here to create it
Liam-Doodson
approved these changes
May 14, 2026
angrykoala
approved these changes
May 14, 2026
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
3 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.
Fixing bug described in #112
Found that the newline results in the resbody being returned as HTML instead of JSON, causing an error with unmarshalling and leading to a panic.
Addressed same issue for a few other commands.