-
Notifications
You must be signed in to change notification settings - Fork 79
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
Terminal settings not restored after aws ecs execute-command #34
Comments
Thank you for reporting this issue! To reproduce it, there is 2 questions: 1, Is there other settings in your container, or would you mind share your dockfile; 2, Is there problem found on other version of linux for you. |
I'm using an image based on If this isn't enough to reproduce the issue, please let me know and I can try to produce a testcase. |
On the client side, I've only tested this on my dev host which runs ubuntu 20.04 which I access via ssh. |
Related: #29 (comment) |
FWIW, in my application which wraps |
Hi, I hope I've found the right place for this bug.
After running
aws ecs execute-command --interactive
, I loose handling of special characters for erase, werase, kill, eof, etc by the terminal. Runningstty icanon
is sufficient to get things working again.I am using version 1.2.295.0 on linux.
I found it necessary to run a shell to reproduce this. Executing /bin/true did not reproduce the issue.
The issue in this case was the
icanon
flag not being reset to it's previous state, but it's a good idea to capture the existing termios settings and restore them before exiting.The text was updated successfully, but these errors were encountered: