fix: query response parser should use UTF-8 encoding#164
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #164 +/- ##
=========================================
Coverage 90.30% 90.30%
Complexity 439 439
=========================================
Files 138 138
Lines 5427 5427
Branches 215 213 -2
=========================================
Hits 4901 4901
Misses 450 450
Partials 76 76
Continue to review full report at Codecov.
|
rhajek
approved these changes
Oct 16, 2020
6a2494e to
f5d53d5
Compare
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
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.
Closes #162
Proposed Changes
The response from InfluxDB server is encoded in UTF-8 =>
InputStreamReadershould use UTF-8 as en encoding.Checklist
mvn testcompletes successfully