-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Executable seemingly a no-op since version 0.9.2 #213
Comments
I've the exact same problem on my MacBook Pro. I checked with bisect which commit is the cause of this change in behavior and found 007dabb (#206). Since this change @anweiss can you please have a look? It would be great to havea a working |
Thanks for reporting!! Sorry about this. Indeed was an oversight on my part. Just released |
Yes, it works all fine now in 0.9.4. Thanks for immediately releasing the new version! |
@anweiss please note that 0.9.2 is busted as well and maybe should also be yanked? |
Yep, both |
Perfect. :) So I assume we can close this issue as well given that everything has been addressed. |
You bet! Re-open if need be. |
Hello! Starting with version 0.9.2, this project's executable stopped responding to command-line arguments and standard input, simply returning with a
0
exit status in all conditions:I have observed this behavior after installing the binary using
cargo
on a Debian VM (via libvert) and on a macOS system. I can also reproduce it using the binaries hosted by GitHub.com on either of those systems:The text was updated successfully, but these errors were encountered: