enterprise-support team mailing list archive

Thread
Date

[Bug 1580436] [NEW] option parsing failed: Invalid byte sequence in conversion input

To: enterprise-support@xxxxxxxxxxxxxxxxxxx
From: Jyrki <jhokkan@xxxxxxxxx>
Date: Wed, 11 May 2016 04:13:49 -0000
Reply-to: Bug 1580436 <1580436@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

both myloader and mydumper fail on option parsing if some option includes non-US ASCII characters. For example:
./mydumper -B mydb -o /tmp/mydb -u user -p xa€Gakdh -h localhost
option parsing failed: Invalid byte sequence in conversion input, try --help

** Affects: mydumper
     Importance: Undecided
         Status: New

** Description changed:

- both myloader and mydumper fail on option parsing some option includes non-US ASCII characters. For example: 
+ both myloader and mydumper fail on option parsing if some option includes non-US ASCII characters. For example:
  ./mydumper -B mydb -o /tmp/mydb -u user -p xa€Gakdh -h localhost
  option parsing failed: Invalid byte sequence in conversion input, try --help

-- 
You received this bug notification because you are a member of Ubuntu
Server/Client Support Team, which is subscribed to MySQL.
Matching subscriptions: Ubuntu Server/Client Support Team
https://bugs.launchpad.net/bugs/1580436

Title:
  option parsing failed: Invalid byte sequence in conversion input

To manage notifications about this bug go to:
https://bugs.launchpad.net/mydumper/+bug/1580436/+subscriptions