Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSON encoding failed: Malformed UTF-8 characters, possibly incorrectly encoded #15628

Closed
OlafvdSpek opened this issue Dec 7, 2019 · 5 comments
Assignees
Labels
Bug A problem or regression with an existing feature
Projects
Milestone

Comments

@OlafvdSpek
Copy link

OlafvdSpek commented Dec 7, 2019

JSON encoding failed: Malformed UTF-8 characters, possibly incorrectly encoded after setting display transformation to Binary to IP for a varbinary column and browsing that table.

5.0.0-rc1

@williamdes williamdes added the Bug A problem or regression with an existing feature label Dec 7, 2019
@williamdes williamdes added this to Needs triage in issues via automation Dec 7, 2019
@williamdes williamdes moved this from Needs triage to to be fixed soon in issues Dec 7, 2019
@Tithugues
Copy link
Contributor

Would it be possible to have a structure and a set of data to reproduce it please?

@goblin2oo8
Copy link

goblin2oo8 commented Jan 17, 2020

I have same bug. Column type binary(16)
Data example INSERT INTO test_table SET ip = INET6_ATON('::ffff:8.8.8.8')
If I use function INET6_NTOA in SELECT query - it is works
But display transformation not working, error write:
JSON encoding failed: Malformed UTF-8 characters, possibly incorrectly encoded

@williamdes
Copy link
Member

williamdes commented Jan 17, 2020

@harsh-kukreja @Gaurav-Punjabi @victorphoenix3 @kartik1000 first one who wants to work on it (if it can be reproduced) comments here :)

Affects 5.0 ?

@kartik1000
Copy link
Contributor

Well I'll first try to reproduce @williamdes and then let you know 😄

@williamdes williamdes self-assigned this Mar 14, 2021
@williamdes williamdes added this to the 5.1.1 milestone Mar 14, 2021
@williamdes
Copy link
Member

CREATE TABLE `aes` (
  `id` int(11) NOT NULL,
  `charreg` varchar(255) NOT NULL,
  `charbin` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
  `vbin` varbinary(255) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

INSERT INTO `aes` (`id`, `charreg`, `charbin`, `vbin`) VALUES
(1, 'ded', 'ded', 0x0ded),
(2, 'ded', 'ded', 0x0ded),
(3, 'fef', 'fef', 0x0fef),
(4, '0x7f000001', '0x7f000001', 0x30783766303030303031);

williamdes added a commit that referenced this issue Mar 14, 2021
Signed-off-by: William Desportes <williamdes@wdes.fr>
williamdes added a commit that referenced this issue Mar 14, 2021
Signed-off-by: William Desportes <williamdes@wdes.fr>
issues automation moved this from to be fixed soon to Closed Mar 15, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A problem or regression with an existing feature
Projects
issues
  
Closed
Development

No branches or pull requests

5 participants