Fix JSON parsing with UTF8 BOM in JSON parser plugin #4099
Merged
Conversation
This file contains 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
danielnelson
pushed a commit
that referenced
this pull request
May 3, 2018
(cherry picked from commit 9647ea8)
|
Thank you! |
jvrahav
pushed a commit
to jvrahav/telegraf
that referenced
this pull request
May 9, 2018
arkady-emelyanov
pushed a commit
to arkady-emelyanov/telegraf
that referenced
this pull request
May 18, 2018
maxunt
pushed a commit
that referenced
this pull request
Jun 26, 2018
otherpirate
pushed a commit
to otherpirate/telegraf
that referenced
this pull request
Mar 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes a bug that is very similar to closed bug #3265.
Required for all PRs: