[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Parallel Bug Reports Wide character in print
From: |
Ole Tange |
Subject: |
Re: GNU Parallel Bug Reports Wide character in print |
Date: |
Sun, 30 Oct 2016 15:18:08 +0100 |
On Sun, Oct 30, 2016 at 2:50 PM, Jean Louis <address@hidden> wrote:
> On Sun, Oct 30, 2016 at 02:34:23PM +0100, Ole Tange wrote:
>> On Sat, Oct 22, 2016 at 12:03 PM, <address@hidden> wrote:
>> > When I do some operations on files with UTF-8 in names, I get:
>> >
>> > Wide character in print at /usr/bin/parallel line 7542
>> >
>> > And it should not be there.
>> >
>> > Using:
>> >
>> > GNU parallel 20160222
>>
>> Give us an MCVE (stackoverflow.com/help/mcve)) and we can look at it.
>
> Sure:
>
> ls čfile.txt | parallel -v --transfer --sshlogin android:8022 echo {}
> parallel: Warning: Could not figure out number of cpus on android:8022 ().
> Using 1.
> Wide character in print at /usr/bin/parallel line 7118.
>
> It happens when transferring files which are in unicode. This time I
> have just chosen android as example server, my phone, but I was
> transferring to other computer.
I cannot reproduce that. I suspect it is due to something in your
environment (maybe the LANG variable?). Therefore please follow
REPORTING BUGS in `man parallel`:
REPORTING BUGS
Report bugs to <address@hidden> or
https://savannah.gnu.org/bugs/?func=additem&group=parallel
See a perfect bug report on
https://lists.gnu.org/archive/html/bug-parallel/2015-01/msg0
0000.html
Your bug report should always include:
· The error message you get (if any).
· The complete output of parallel --version. If you are
not running the latest released version (see
http://ftp.gnu.org/gnu/parallel/) you should specify why
you believe the problem is not fixed in that version.
· A minimal, complete, and verifiable example (See
description on http://stackoverflow.com/help/mcve).
It should be a complete example that others can run that
shows the problem including all files needed to run the
example. This should preferably be small and simple, so
try to remove as many options as possible. A combination
of yes, seq, cat, echo, and sleep can reproduce most
errors. If your example requires large files, see if you
can make them by something like seq 1000000 > file or
yes | head -n 10000000 > file. If your example requires
remote execution, see if you can use localhost - maybe
using another login.
· The output of your example. If your problem is not
easily reproduced by others, the output might help them
figure out the problem.
· Whether you have watched the intro videos
(http://www.youtube.com/playlist?list=PL284C9FF2488BC6D1),
walked through the tutorial (man parallel_tutorial), and
read the EXAMPLE section in the man page (man parallel -
search for EXAMPLE:).
If you suspect the error is dependent on your environment
or distribution, please see if you can reproduce the error
on one of these VirtualBox images:
http://sourceforge.net/projects/virtualboximage/files/
http://www.osboxes.org/virtualbox-images/
Specifying the name of your distribution is not enough as
you may have installed software that is not in the
VirtualBox images.
If you cannot reproduce the error on any of the VirtualBox
images above, see if you can build a VirtualBox image on
which you can reproduce the error. If not you should
assume the debugging will be done through you. That will
put more burden on you and it is extra important you give
any information that help. In general the problem will be
fixed faster and with less work for you if you can
reproduce the error on a VirtualBox.
/Ole
PS: Neat email address.