Open EduardoSantanaSeverino opened 1 year ago
Appreciate you letting us know @EduardoSantanaSeverino We'll post any updates on this thread. Please :+1: and comment if you're also seeing this issue as it helps us gauge impact.
I've noticed this bug still exists (version v0.2023.06.27.19.34.stable_01) - took me a couple of minutes to figure out that it was Warp's issue, not my ssh configuration 😅 Hope it'll be fixed soon 🙏🏼
Thanks a lot :) Warp is a great tool 💪🏼
I'm also getting when running:
17:04 ~/ λ ssh git@github.com
PTY allocation request failed on channel 0
Hi nbbaier! You've successfully authenticated, but GitHub does not provide shell access.
Connection to github.com closed.
I'm also getting when running:
17:04 ~/ λ ssh git@github.com PTY allocation request failed on channel 0 Hi nbbaier! You've successfully authenticated, but GitHub does not provide shell access. Connection to github.com closed.
I have the same issue.
Same issue here. Preventing pty with -T
does indeed work.
Running the same command (without -T
) in any other terminal works fine.
Discord username (optional)
No response
Describe the bug
When trying to test the SSH connection to GitHub, I am getting the "PTY allocation request failed on channel 1".
To Reproduce
Steps to reproduce:
Expected behavior
No response
Screenshots
Operating System
MacOS
OS Version
13
Shell Version
zsh 5.9 (x86_64-apple-darwin22.0)
Warp Version
v0.2023.04.11.08.03
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None