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

Please add a way to specify the license file location #142

Open
thht opened this issue May 17, 2024 · 3 comments
Open

Please add a way to specify the license file location #142

thht opened this issue May 17, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@thht
Copy link

thht commented May 17, 2024

Hi,
we're running Matlab in an apptainer container. This runs on a cluster node we connect to via ssh using the VS Code Remote SSH extension. The container image is public so we cannot put any license information in there. The workaround so far is to specify the license server as an environment variable. This works fine when running slurm jobs and starting matlab from the shell etc. But the VS Code extension does not seem to care about the env variable so it starts the activation app. This fails if the user is connecting from a windows machine because activation needs X which the user does not have. (It works fine from Linux because X11 forwarding is enabled. Still, not ideal because just checking out from the lic server would be more convenient).

I would like to suggest to add a preference to the extension similar to the -c command line switch, so users can enter their license location. Alternatively one could make sure to honor the environment variable which I have checked is visible when I open a terminal!

Thanks!

@thht thht added the enhancement New feature or request label May 17, 2024
@dklilley
Copy link
Member

Hi @thht, thanks for raising this to us!

Can you clarify which environment variable you are referring to?

@thht
Copy link
Author

thht commented May 21, 2024

I'm referring to the MLM_LICENSE_FILE env variable.

@dklilley
Copy link
Member

Thanks for the clarification!

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

No branches or pull requests

2 participants