Warp
Warp copied to clipboard
warpdotdev
[Bug] Running ssh command alias throwing error
Discord username (optional)
No response
Describe the bug
"ssh hostname -N -D hostname 2>/dev/null &" throws following error
Failed to bootstrap warp. Continuing with a non-bootstrapped shell.
To Reproduce
Running an alias with the command "ssh hostname -N -D hostname 2>/dev/null &"
Expected behaviour
No response
Screenshots
No response
Operating System
MacOS
OS Version
12.5.1
Shell Version
bash 3.2.57
Warp Version
v0.2022.09.07.14.56.stable_00
Additional context
No response
Does this block you from using Warp daily?
Yes
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
No response
Hi @selfishtoaster, I'm Danny, Support Engineer at Warp. So sorry to hear you having issues with ssh. I've tried to reproduce this on my end but not getting the same error you're seeing ( although I am getting an error, it's the same on iterm/terminal ). I also found that running the command without the & at the end produces no error, but also no result.
As a stopgap measure, please try and disable the SSH Wrapper in the Settings > Features menu, then run the command again.
If you can please provide some redacted screenshots of your issue, and the expected result as it would also help us narrow down the cause.
I will post any updates to this here.
No luck yet, but I'm starting to wonder if if something with work laptop
On Fri, Sep 16, 2022, 1:18 PM Danny Neira @.***> wrote:
@selfishtoaster https://github.com/selfishtoaster Any luck with the above?
— Reply to this email directly, view it on GitHub https://github.com/warpdotdev/Warp/issues/1831#issuecomment-1249776021, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXKPAPVFPI23DIQFH3JRJ3LV6TI27ANCNFSM6AAAAAAQLQG7MY . You are receiving this because you were mentioned.Message ID: @.***>
A screenshot of your issues may be helpful, but my guess is that you may have a custom prompt and that Warp is unable to parse it.
You can check whether it’s something in your dotfiles by setting up clean configs:
Set
ZDOTDIR=/
in your
~/.zshenv
file. This forces Zsh to run with zero configs.
You can disable parts of your dotfiles just for Warp by using this conditional statement:
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
##### WHAT YOU WANT TO DISABLE FOR WARP - BELOW
# Whatever you want to disable
##### WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi
We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on custom prompts here: https://docs.warp.dev/features/prompt I hope that helps.
Thank you I will try that
On Fri, Sep 16, 2022, 1:43 PM Danny Neira @.***> wrote:
A screenshot of your issues may be helpful, but my guess is that you may have a custom prompt and that Warp is unable to parse it. https://docs.warp.dev/features/prompt#ps1-compatibility-table
You can check whether it’s something in your dotfiles by setting up clean configs: https://docs.warp.dev/help/known-issues#configuring-and-debugging-your-rc-files Set ZDOTDIR=/ in your ~/.zshenv file. This forces Zsh to run with zero configs.
You can disable parts of your dotfiles just for Warp by using this conditional statement:
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
WHAT YOU WANT TO DISABLE FOR WARP - BELOW
Whatever you want to disable
WHAT YOU WANT TO DISABLE FOR WARP - ABOVE
fi
We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on custom prompts here: https://docs.warp.dev/features/prompt I hope that helps.
— Reply to this email directly, view it on GitHub https://github.com/warpdotdev/Warp/issues/1831#issuecomment-1249793795, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXKPAPVJNYU52NQGVCWOJZTV6TLV3ANCNFSM6AAAAAAQLQG7MY . You are receiving this because you were mentioned.Message ID: @.***>
Great, let me know if that helps at all @selfishtoaster
If not we may need some screenshots or a video of your issue and the expected result so that we can work to reproduce it on our end.
@selfishtoaster Another quick follow-up to see if the above was helpful at all. Looking forward to hearing from you.