libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <>
Subject [jira] [Commented] (LIBCLOUD-491) ParamikoSSHClient don't show stdout/stderr when run fast commands
Date Fri, 10 Jan 2014 14:35:56 GMT


Tomaz Muraus commented on LIBCLOUD-491:

[~gigimon] OK, I've pushed a fix to the trunk -;a=commitdiff;h=b6d79be;hp=b6ada523b3493c765b3e1cd164a889e1e22167f9

I've manually tested it and confirmed it's working.

[~jc2k] Yeah, existing code in Libcloud isn't pretty either, but I couldn't come up with a
nicer approach which would still handle all the edge cases.

I'll also look into adding some integration tests. To being with, just a simple script which
tests all the edge cases and needs to be run manually on an existing server should be an improvement.

> ParamikoSSHClient don't show stdout/stderr when run fast commands
> -----------------------------------------------------------------
>                 Key: LIBCLOUD-491
>                 URL:
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: Oleg Suharev
>            Priority: Critical
> Hello
> Commit a053cde create a big trouble in method. When I run 'fast'
commands (for example uname -a) this method doesn't return stdout/stderr, because code
> {code}
> while not chan.exit_status_ready():
>             if chan.recv_ready():
> {code}
> doesn't run since chan.exit_status_ready() already return True (in first call)
> [~kami] please fix this trouble.
> {code}
> In [1]: from libcloud.compute.ssh import SSHClient
> In [2]: client = SSHClient('123.123.321.321', key='/Users/user/mykey.pem')
> In [3]: client.connect()
> Out[3]: True
> In [4]:'uname -a')
> Out[4]: ['', '', 0]
> {code}

This message was sent by Atlassian JIRA

View raw message