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

Message is not correctly displayed for cluster_log table #16964

Closed
Ishiihara opened this issue Apr 30, 2020 · 2 comments · Fixed by #19648
Closed

Message is not correctly displayed for cluster_log table #16964

Ishiihara opened this issue Apr 30, 2020 · 2 comments · Fixed by #19648
Assignees
Labels
severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Ishiihara
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?

mysql> select * from cluster_log where level='warn' limit 1\G
*************************** 1. row ***************************
    TIME: 2020/04/30 09:59:16.908
    TYPE: tidb
INSTANCE: 127.0.0.1:4000
   LEVEL: WARN
 MESSAGE: 0x5B626173655F636C69656E742E676F3A3137305D205B225B70645D206661696C656420746F2067657420636C7573746572206964225D205B75726C3D687474703A2F2F3132372E302E302E313A323337395D205B6572726F723D226572726F723A727063206572726F723A20636F6465203D20556E617661696C61626C652064657363203D20616C6C20537562436F6E6E732061726520696E205472616E7369656E744661696C7572652C206C617465737420636F6E6E656374696F6E206572726F723A20636F6E6E656374696F6E206572726F723A2064657363203D205C227472616E73706F72743A204572726F72207768696C65206469616C696E67206469616C20746370203132372E302E302E313A323337393A20636F6E6E6563743A20636F6E6E656374696F6E20726566757365645C22207461726765743A3132372E302E302E313A32333739207374617475733A5452414E5349454E545F4641494C555245225D
1 row in set (0.01 sec)

2. What did you expect to see?

The MESSAGE field is expect to be a string of similar to [grpclog.go:60] ["transport: http2Server.HandleStreams failed to read frame: read tcp 127.0.0.1:2382->127.0.0.1:57030: use of closed network connection"]

3. What did you see instead?

0x5B626173655F636C69656E742E676F3A3137305D205B225B70645D206661696C656420746F2067657420636C7573746572206964225D205B75726C3D687474703A2F2F3132372E302E302E313A323337395D205B6572726F723D226572726F723A727063206572726F723A20636F6465203D20556E617661696C61626C652064657363203D20616C6C20537562436F6E6E732061726520696E205472616E7369656E744661696C7572652C206C617465737420636F6E6E656374696F6E206572726F723A20636F6E6E656374696F6E206572726F723A2064657363203D205C227472616E73706F72743A204572726F72207768696C65206469616C696E67206469616C20746370203132372E302E302E313A323337393A20636F6E6E6563743A20636F6E6E656374696F6E20726566757365645C22207461726765743A3132372E302E302E313A32333739207374617475733A5452414E5349454E545F4641494C555245225D

4. What version of TiDB are you using? (tidb-server -V or run select tidb_version(); on TiDB)

mysql> select tidb_version();
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version()                                                                                                                                                                                                                                                                                         |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v4.0.0-beta.2-352-g5ede18f10e
Git Commit Hash: 5ede18f10eedfe2e3690d7728dec3ffa4b0af2d5
Git Branch: HEAD
UTC Build Time: 2020-04-26 12:08:15
GoVersion: go1.13.4
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
@Ishiihara Ishiihara added the type/bug The issue is confirmed as a bug. label Apr 30, 2020
@Ishiihara
Copy link
Author

Looks like the message doesn't display correctly for mysql 8.0 client.

$ mysql --version
mysql  Ver 8.0.19 for osx10.15 on x86_64 (Homebrew)

@crazycs520
Copy link
Contributor

@Ishiihara Thanks for your report. This should be fixed in #19648.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants