Re: [orca-list] Plan to release new pre-release of Orca 3.32 ?

[Didier Spaier <didier slint fr>]

On 14/01/2019 18:36, Samuel Thibault wrote:
> Usually it takes less human time to bisect, which directly tells which
> piece of code is involved, than trying to find out directly.

No luck, going back to 3.10.

But I see this in src/orca/orca_bin.py:

def otherOrcas():
    """Returns the pid of any other instances of Orca owned by this user."""

    openFile = subprocess.Popen('pgrep -u %s orca' % os.getuid(),
                                shell=True,
                                stdout=subprocess.PIPE).stdout
    pids = openFile.read()
    openFile.close()
    orcas = [int(p) for p in pids.split()]

    pid = os.getpid()
    return [p for p in orcas if p != pid]

OTOH:

didier[~]$ ps -eLf|grep -w orca$
didier    5256     1  5256  4    5 20:05 tty1     00:04:20 orca
didier    5256     1  5363  0    5 20:05 tty1     00:00:00 orca
didier    5256     1  5364  0    5 20:05 tty1     00:00:00 orca
didier    5256     1  5368  0    5 20:05 tty1     00:00:00 orca
didier    5256     1  5429  0    5 20:05 tty1     00:00:05 orca
didier[~]$ 

Could it be that the function otherOrcas() finds e.g. 5363 != 5256
hence triggers the error message that we see elsewhere in the same file:

    if otherOrcas():
        print(messages.CLI_OTHER_ORCAS_ERROR)
        return 1

printed in messages.py:
     if otherOrcas():
        print(messages.CLI_OTHER_ORCAS_ERROR)
        return 1

???