pt-deadlock-logger incorrectly parses event_scheduler transaction info

[Геннадий]

Command: pt-deadlock-logger --ask-pass --user=percona_toolkit

percona-toolkit version: 2.2.19
MySQL version: Percona Server 5.7.15-9

Output(replaced actual queries/username/etc):
Enter MySQL password:
server ts thread txn_id txn_time user hostname ip db tbl idx lock_type lock_mode wait_hold victim query
localhost 2016-12-01T14:45:01 72356 0 0 user 127.0.0.1 db table PRIMARY RECORD X w 1 query
localhost 2016-12-01T14:45:01 73143 0 1 Sending event_scheduler db table KEY RECORD S w 0 query

Input:
mysql> show engine innodb status\G
...
------------------------
LATEST DETECTED DEADLOCK
------------------------
...
MySQL thread id 67674, OS thread handle 140422288205568, query id 815917461 event_scheduler Sending data
...

Problem:
pt-deadlock-logger parses "event_scheduler" as a hostname and "Sending" as a user.

[Sveta Smirnova (svetasmirnova)]

Thank you for the report.

Verified as described:

sveta@Thinkie:~/issues$ ~/src/percona-toolkit/bin/pt-deadlock-logger --ask-pass --user=root --host=127.0.0.1 --port=13001
Enter MySQL password:
DBI connect(';host=127.0.0.1;port=13001;mysql_read_default_group=client','root',...) failed: Access denied for user 'root'@'localhost' (using password: YES) at /home/sveta/src/percona-toolkit/bin/pt-deadlock-logger line 2427.
sveta@Thinkie:~/issues$ echo $?
2
sveta@Thinkie:~/issues$ ~/src/percona-toolkit/bin/pt-deadlock-logger --version
pt-deadlock-logger 2.2.19

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-1401