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

TypeError when applying nix environment in Remote SSH #81

Open
siddharth-krishna opened this issue Jun 27, 2023 · 3 comments
Open

TypeError when applying nix environment in Remote SSH #81

siddharth-krishna opened this issue Jun 27, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@siddharth-krishna
Copy link

Describe the bug
I am using this extension from VS Code on my macbook, and using the Remote SSH extension to open a workspace on a remote Ubuntu server. The wokspace has nix flakes set up. When I try to select a nix environment using this extension, the message "Applying environment" appears forever, but in the "Extension Host (Remote)" output pane I see the error:

2023-06-27 07:25:22.142 [error] TypeError: c.call is not a function
	at /home/sid/.vscode-server/extensions/arrterian.nix-env-selector-1.0.9/dist/main.js:2538:310

To Reproduce
Steps to reproduce the behavior:

  1. Open a remote workspace.
  2. Use the "Nix-Env: Select environment" command to select flake.nix
  3. Open the Outputs pane and go to "Extension Host (Remote)"
  4. See error

Expected behavior
I expect the nix environment to be activated so that I can use HLS for my project.

Environment:

  • OS: macOS 13.4.1
  • VS Code: 1.79.2
@siddharth-krishna siddharth-krishna added the bug Something isn't working label Jun 27, 2023
@nh2
Copy link
Contributor

nh2 commented Oct 14, 2023

@arrterian Could I sponsor some work on this one? Let me know!

@arrterian
Copy link
Owner

@nh2 I've been juggling a lot since I joined the Ukrainian Armed Forces. So, there is no chance to work on the extension any soon.
You have done amazing work in previous PR.
If you can contribute to this one, it will be awesome.

@nh2
Copy link
Contributor

nh2 commented Feb 2, 2024

juggling a lot since I joined the Ukrainian Armed Forces. So, there is no chance to work on the extension any soon.

@arrterian That is very understandable. I hope it goes well!


I already had some look into c.call is not a function when I first found this issue.

Unfortunately, my understanding of Clojure and its transpilation to JavaScript is very low. I cannot tell whether this is a bug in the code, or a bug in the transpiler.

The fact that the whole thing is untyped all the way through makes it difficult to figure out on which level things are going wrong. I suspect TypeScript might make this extension simpler to contribute to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants