stdin / stdout behaves really weirdly at random

[wbobeirne]

Came back to a terminal session after a while and got this behavior:

It wasn't showing my input, and line breaks didn't seem to be working. My input was roughly

• echo wtf
• ls -la
• enter a bunch of times
• ls -la

Not sure what caused this, but it happened in two separate instances.

[ammario]

I can't seem to replicate it. If you're good at replicating it, see if it happens in the web terminal?

[sreya]

This happens every time I exit a remote session.

➜  ~ coder sh jon
[coder@jon ~]$ ls
bin  core.nxagent.4006660.1588321611  globalStorageHome  go  istio-1.3.0  lost+found  src
[coder@jon ~]$ exit
exit
➜  ~ ls
Applications  Documents  Library  Music     Public  csums  google-cloud-sdk
                                                                           Desktop       Downloads  Movies   Pictures  bin     go     src
                          %                                                                                    ➜  ~ 

[ammario]

#11 will likely fix this.

[scsmithr]

@wbobeirne It's hard to tell from your gif, but was this while you were still connected to the env, or was this after a disconnect?

[wbobeirne]

Just had it happen again, I was disconnected, it happened after being away from my machine for a while so presumably it went to sleep and lost connectivity.

[scsmithr]

Can you try reinstalling using the latest master? We didn't restore the terminal state on exit, causing everything to be weirdly offset.

[wbobeirne]

Can confirm this is now fixed, was incorrectly updating my binary (needed that -u flag)