gigalixir / gigalixir-cli

MIT License
52 stars 45 forks source link

Pseudo-terminal will not be allocated because stdin is not a terminal #99

Closed toranb closed 2 years ago

toranb commented 2 years ago

I noticed last week that ssh fails trying to ssh in for migrations with the following args

'['ssh', '-t', 'root@v2018-us-central1.gcp.ssh.gigalixir.com', '-p', '31632', 'gigalixir_run', 'migrate']'

if you instead use -tt or possibly -T I think you can side step this because that option will Disable pseudo-tty allocation

Any help on this would be greatly appreciated @jesseshieh

If I use the -o options I still see gigalixir ssh_helper using the normal -t option

gigalixir ps:ssh -o "-tt"

'['ssh', '-tt', '-t', 'root@v2018-us-central1.gcp.ssh.gigalixir.com', '-p', '31632', 'gigalixir_run', 'migrate']'

edit this terminal error fails during any Github Actions Deployment that requires gigalixir

Screen Shot 2022-05-09 at 4 09 34 PM
gigatim commented 2 years ago

We added support for -o "-T". That should disable -t. I'm not seeing -tt as an SSH option on my linux setup, is that a OS X based option?

toranb commented 2 years ago

Interestingly the -T option just hangs forever. The -tt option seems to land me a valid ssh session. Good news is that this did solve my problem using gigalixir with github actions :) so thank you for the speedy turn around last night!

Screen Shot 2022-05-10 at 9 57 54 AM

I learned that -t -t shorthand is -tt from this stackoverflow question