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

Can't click "show details" on sssh connection error #21

Closed
Jason-Morcos opened this issue Jun 16, 2020 · 10 comments · Fixed by #22
Closed

Can't click "show details" on sssh connection error #21

Jason-Morcos opened this issue Jun 16, 2020 · 10 comments · Fixed by #22

Comments

@Jason-Morcos
Copy link
Member

I get the error "The SSH Tunnel has unexpectedly closed.". When I click Show Detail, the popup disappears without telling me why.

@Jason-Morcos
Copy link
Member Author

Jason-Morcos commented Jun 16, 2020

@gboudreau I'm not sure what's causing this one. I too had the show details button working a few commits ago. Perhaps sandboxing interrupted this too? Or perhaps it was unrelated

@Jason-Morcos
Copy link
Member Author

Perhaps it was related to this fix?

437a0bd

@gboudreau
Copy link
Contributor

gboudreau commented Jun 16, 2020

I can take a look, if you are not already on it..?
*edit: No, the problem isn't 437a0bd; I tried reversing only that commit, and the problem is still there. I'll just use git bisect to find the culprit.
*edit 2: seems to be caused by 0c390d3

@jamesstout
Copy link
Contributor

Hmmm, sorry fellas. I tested that quite a bit as well...

@gboudreau
Copy link
Contributor

Some of the return codes used in SPConnectionController (but not all of them) are defined in SPAlertSheets.m
If we change them in that file, then we'll need to change the returnCodes used in the conditionals everywhere SPAlertSheets is used.
But I also noticed that sometimes, a regular NSAlert is used, and return codes needs to use the deprecated values, until those NSAlert are updated (to use completionHandler: instead of a didEndSelector: ..?)

@gboudreau
Copy link
Contributor

Overall, removing all deprecated notices would need some effort in that regard.
I suggest just reverting the modified conditionals, until someone takes more time to resolve the issue globally.

@gboudreau
Copy link
Contributor

Of note: NSOKButton => NSModalResponseOK can be kept, as those two are equivalent.

@Jason-Morcos
Copy link
Member Author

Does this fix it for everyone? I accept both the new and legacy conditional values

7805a4b

@jamesstout
Copy link
Contributor

Tested ssh fails last night and looked good (not the bind error though, not sure how to replicate). Didn't get chance to check fav import fails or bundle deletes, but for those two I'd changed them to the withCompletion instantiation. I'll check later.

Just FYI - I'm back to work now and in Hong Kong (GMT+8).

@jamesstout
Copy link
Contributor

jamesstout commented Jun 17, 2020

fav import failure just displays one OK button and return code isn't checked.
delete bundle - OK and cancel work as expected.
delete favourite - OK and cancel work as expected.

ssh bad username - buttons work as expected
ssh wrong IP - buttons work as expected
ssh wrong port - buttons work as expected
ssh no key or pass - buttons work as expected
ssh bad key (edit ~/.ssh/id_rsa) - buttons work as expected
revert edit and re-select key - connection fails. Maybe not copied to .keys? It is. Needs a bit more testing. Sometimes works sometimes doesn't. But a very rare case for people to be manually editing keys.
cp ~/.ssh/id_rsa.bak to ~/.ssh/id_rsa and re-select key - connection works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants