- Notifications
You must be signed in to change notification settings - Fork16
Remove HostName from SSH config#336
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
It is not necessary because the proxy command is what is in control hereand having HostName causes errors in Gateway about the host not beingfound even though it seems to work in the end.
abe05dd
to9d7b2f1
CompareQodana Community for JVM54 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get -name:'Qodana Scan'uses:JetBrains/qodana-action@v2023.2.8with:upload-result:true Contact Qodana teamContact us atqodana-support@jetbrains.com
|
Uh oh!
There was an error while loading.Please reload this page.
Having
HostName
causes errors in Gateway about the host not being found even though it seems to work in the end...but all those (many, many) errors make the logs noisy and maybe this is causing some instability in some cases.I have no idea why Gateway is trying to connect to
HostName
when there is aProxyCommand
but it smells like a bug.For now I removed
HostName
and there are no more errors. It was just copied from how the Coder CLI does things so hopefully it is not actually required somehow because I have no idea why it was included in the first place. Everything works for me without it.