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
support running in remote extension host #76
Conversation
Use the same trick, as in eslint plugin here: https://github.com/microsoft/vscode-eslint/blob/f71e3089a0e63c9b4e94f1ea4264f90599f5ddab/server/src/eslintServer.ts#L502
Hi @kalinkrustev , Thanks for the PR, but I'm not sure what the effect of this change. And in fact, that's not what #41 is about. The idea behind #41 is to enable the extension to work on remotes like SSH, WSL, Container, without the need to install the extension on that remote. To accomplish this, a few changes (API and contributing related) needs to be made. Could you please provide more details about the meaning of this change? Thank you |
OK, I am not sure how easy it is to achieve that without installing the extension at the remote. My proposal makes it work when the extension is installed at the remote. The effect of this change is to use the original require, not the webpack one, to read the contents from |
The If that's not your scenario, there will be no need to install the extension on the remote (once it is updated to work with remotes). The extension should be installed only locally, and it would work correctly on any remote (Container, WSL, SSH, Codespaces). I mean, if your // can also return a promise of required JSON structure
module.exports = [{
"url": "http://127.0.0.1:8080/job/myproject/",
"name": "Jenkins Build",
"username": "jenkins_user",
"password": "jenkins_password_or_token"
},
{
"url": "http://127.0.0.1:8080/job/myprojectTests/",
"name": "Jenkins Acceptance Tests",
"username": "jenkins_user",
"password": "jenkins_password_or_token"
}]; You could easily change to the [
{
"url": "http://127.0.0.1:8080/job/myproject/",
"name": "Jenkins Build",
"username": "jenkins_user",
"password": "jenkins_password_or_token"
},
{
"url": "http://127.0.0.1:8080/job/myprojectTests/",
"name": "Jenkins Acceptance Tests",
"username": "jenkins_user",
"password": "jenkins_password_or_token"
}
] And it has the same effect. |
I need it to be |
That's really weird the extension to have issues loading Using your snippet, it indeed does work, and I'll apply it to this scenario. But in order to keep the extension easier to use (installed locally and working on remotes), other changes are needed (the regular support remotes approach). This will support the default Thank you |
Closing, in favor of #78 |
Use the same trick, as in eslint plugin here:
https://github.com/microsoft/vscode-eslint/blob/f71e3089a0e63c9b4e94f1ea4264f90599f5ddab/server/src/eslintServer.ts#L502