Skip to content
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

Trouble logging in with warp terminal #2

Open
bentsai opened this issue Apr 27, 2022 · 2 comments
Open

Trouble logging in with warp terminal #2

bentsai opened this issue Apr 27, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@bentsai
Copy link

bentsai commented Apr 27, 2022

I had trouble logging in with warp. (It works fine with iTerm2).

ssh lists.sh
Connection to lists.sh closed.

It may be particular to my machine, so feel free to close, but wanted to document (here is verbose mode):

debug1: Offering public key: /Users/bbt/.ssh/id_rsa RSA SHA256:B78q7Sgg2PGBr5WxKYQgVgFZtpJG0TzraXbW4cb9WsQ
debug1: Server accepts key: /Users/bbt/.ssh/id_rsa RSA SHA256:B78q7Sgg2PGBr5WxKYQgVgFZtpJG0TzraXbW4cb9WsQ
debug1: Authentication succeeded (publickey).
Authenticated to lists.sh ([143.198.19.169]:22).
debug1: setting up multiplex master socket
debug1: channel 0: new [/Users/bbt/.ssh/165103009231089]
debug1: channel 1: new [client-session]
debug1: Entering interactive session.
debug1: pledge: id
debug1: Sending environment.
debug1: channel 1: setting env LC_ALL = "en_US.UTF-8"
debug1: Sending command:
                         printf '\033P$d{"hook": "SSH", "value": {"socket_path": "~/.ssh/165103009231089", "user": "%s", "machine": "%s", "remote_shell": "%s"}}\234' $(whoami) $(hostname) ${SHELL##*/}

                                                                                        if test "${SHELL##*/}" != "bash" -a "${SHELL##*/}" != "zsh"; then
                                           exec $SHELL
                                                      fi

                                                        case ${SHELL##*/} in
                                                                              bash) exec -a bash bash --rcfile <(echo 'set -o vi; set +o vi; HISTCONTROL=ignorespace; printf '\\''\033P$d{"hook": "InitShell", "value": {"shell": "bash"}}\234'\\''')
                            ;;
                                zsh) WARP_TMP_DIR=$(mktemp -d warptmp.XXXXXX)
                                                                             if [[ $? == 0 ]]; then
                                                                                                   echo '756e7365746f7074205a4c453b20756e736574205243533b20756e736574
                                                     20474c4f42414c5f5243533b207072696e746620275c7831625c7835305c
 7832345c7836347b22686f6f6b223a2022496e69745368656c6c222c2022
                                                             76616c7565223a207b227368656c6c223a20227a7368227d7d5c78396327' | command xxd -ps -r > $WARP_TMP_DIR/.zshenv
                                                       else
                                                           echo "Failed to bootstrap warp. Continuing with a non-bootstrapped shell."
                     fi
                       T
debug1: client_input_channel_req: channel 1 rtype exit-status reply 0
debug1: channel 1: free: client-session, nchannels 2
debug1: channel 0: free: /Users/bbt/.ssh/165103009231089, nchannels 1
Connection to lists.sh closed.
Transferred: sent 4520, received 1348 bytes, in 0.1 seconds
Bytes per second: sent 89192.3, received 26599.8
debug1: Exit status 0
@neurosnap
Copy link
Owner

Hey thanks for taking the time to submit this bug report!

The command being sent looks a little peculiar, I'll spend some time debugging and see what I discover.

@bentsai
Copy link
Author

bentsai commented Apr 27, 2022

You're welcome – this project is so up my alley.

I acknowledge that warp is quite new and different, so I understand if this is low priority. Since I can use other terminals, I can easily work around it. But still, figured it's good for you to know to potentially make something on your end more robust, etc.

@neurosnap neurosnap added the bug Something isn't working label Apr 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants