Skip to content

Conversation

@frol
Copy link

@frol frol commented Sep 24, 2015

Here is the issue reproduction:

import invoke
invoke.run(u'echo \xff', pty=True)

Here is the issue reproduction:

```python
import invoke
invoke.run(u'echo \xff', pty=True)
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • E501 line too long (81 > 79 characters)

@frol
Copy link
Author

frol commented Sep 24, 2015

@bitprophet I discovered this bug while improving integration tests for my #274

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • W293 blank line contains whitespace

@frol
Copy link
Author

frol commented Sep 24, 2015

Everything is tested and Travis is happy. Please, merge.

@bitprophet bitprophet added this to the 0.12 milestone Sep 25, 2015
@bitprophet bitprophet removed this from the 0.12 milestone Dec 21, 2015
@frol
Copy link
Author

frol commented Feb 18, 2016

@bitprophet You seem to neglect PRs which target stability. This is why I decided to provide even more obvious reproduction:

import invoke
try:
    invoke.run(u'echo \xff', pty=True)
except:
    pass
print("This must be printed ONCE!")
$ env LANG=C python bug_275.py
This must be printed ONCE!
This must be printed ONCE!

The text "This must be printed ONCE!" is printed TWICE because of an exception which happens when execv fails. In this case, it fails due to another bug (fixed in #274 (yet again, not merged for almost half a year now)):

  File "/tmp/env/lib/python2.7/site-packages/invoke/runners.py", line 741, in start
    os.execv('/bin/bash', ['/bin/bash', '-c', command])
TypeError: execv() arg 2 must contain only strings

@bitprophet
Copy link
Member

You seem to neglect PRs which target stability.

Casting shade on the maintainer is not good feedback. You don't seem to value volunteer time very much going by this and past comments. I get that my slow pace is frustrating, but you need to understand this is all a labor of love and try dialing back the entitlement a little bit please! :) thanks!

(And thanks also for the detailed repro! I don't think I had tried reproducing this yet but the extra details make it much clearer.)

@frol
Copy link
Author

frol commented Feb 20, 2016

@bitprophet It is frustrating to see that my volunteer time (and other PRs also) is left behind, while I see new commits are made. Please, prioritize PRs reviews and either close them or merge before you proceed. Otherwise, PRs are just useless.

I have some time for open-source, but I want to make it better, not to waste my time on it.

@frol
Copy link
Author

frol commented Apr 11, 2016

I have merged this into #274 since the tests failing badly otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants