On the cmd line I can successfully do ...
$ git clone git@raspi4:sudoku
...
Receiving objects: 100% (35/35), 13.19 KiB | 2.64 MiB/s, done.
In sourcetree, I see ...
ssh: connect to host raspi4 port 22: Undefined error: 0
fatal: Could not read from remote repository.
This happens on MacOS after an upgrade to Sequoia.
Well, this is broken on one of my Sequoia-updated machines but isn't on another Sequoia-updated machine ... so perhaps it's not automatically a Sequoia issue.
Not quite sure how to debug the SSH connection that happens during the SourceTree-UI-initiated "git pull" command. Note that a "git pull" works well for me from my command line (on both machines) but not from the SourceTree UI.
How can I be sure that the SSH details from SourceTree's "git pull" command is the same as my iTerm-initiated "git pull" command? What environment variables might be different across the two "git pull" commands? How can I turn on enough logging (e.g., ssh -vvv ...) to see exactly where the SourceTree-initiated "git pull" breaks within the SSH command?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue here.
Some programs have been having problems on the network since Sequoia. Really weird.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.