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

License activate load infinity on MAC mini M1 #271

Open
erufenix opened this issue Feb 22, 2024 · 16 comments
Open

License activate load infinity on MAC mini M1 #271

erufenix opened this issue Feb 22, 2024 · 16 comments

Comments

@erufenix
Copy link

What happened?

When you activate the license, it charges for a long time. This happens on a Mac mini M1 with Sonoma

I've already uninstalled and installed it several times and it's still the same.

The same one on my laptop with Linux works correctly

loadNinjaMac

Version

1.0.288

Steps to reproduce (or sample repo)

Console Ninja: Activate License

Log output

16:59:09.350 info extension stopping host
16:59:09.355 ERR! extension host process error: spawn /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) ENOENT
16:59:13.587 ERR! extension host process error: spawn /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) ENOENT
@smcenlly
Copy link
Member

It looks like somehow your Console Ninja extension became corrupted on your Mac mini M1.

Can you please do the following:

  1. Uninstall the Console Ninja extension
  2. Close all instances of VS Code
  3. Delete the ~/.vscode/extensions/wallabyjs.console-ninja-1.0.288 from, your home directory
  4. Re-open VS Code
  5. Install the Console Ninja extension

If that does not work and you're still having problems, please let us know.

@smcenlly
Copy link
Member

Assuming our suggestion fixed your problem; closing this issue.

If you're still having problems, please let us know and we'll re-open the issue.

@erufenix
Copy link
Author

It looks like somehow your Console Ninja extension became corrupted on your Mac mini M1.

Can you please do the following:

1. Uninstall the Console Ninja extension

2. Close all instances of VS Code

3. Delete the `~/.vscode/extensions/wallabyjs.console-ninja-1.0.288` from, your home directory

4. Re-open VS Code

5. Install the Console Ninja extension

If that does not work and you're still having problems, please let us know.

I've done this several times and the same problem continues.

@smcenlly smcenlly reopened this Feb 28, 2024
@smcenlly
Copy link
Member

Can you please edit your preferences JSON file with Preferences: Open User Settings (JSON) and add a setting:

...
  "console-ninja.node": "your path to node"
...

Change your path to node with your actual node path. You should be able to find this from the command-line with which node or where node.


Please let us know if that works for you.

@erufenix
Copy link
Author

erufenix commented Mar 1, 2024

It is not solved, the problem continues

"console-ninja.node": "/opt/homebrew/bin/node",

@ArtemGovorov
Copy link
Member

@erufenix Can you please run:

> /opt/homebrew/bin/node -v

in your terminal share the output?

@erufenix
Copy link
Author

erufenix commented Mar 6, 2024

v21.6.2

@smcenlly
Copy link
Member

smcenlly commented Mar 7, 2024

Can you please provide us with the zipped contents of your Console Ninja extension directory? If you are using the latest version, it should be located here:

~/.vscode/extensions/wallabyjs.console-ninja-1.0.290

@erufenix
Copy link
Author

Can you please provide us with the zipped contents of your Console Ninja extension directory? If you are using the latest version, it should be located here:

~/.vscode/extensions/wallabyjs.console-ninja-1.0.290

console-ninja_eru.tar.gz

@ArtemGovorov
Copy link
Member

@erufenix Thanks for providing the extension's archive. We have inspected it and everything looks expected, so neither corrupted extension installation, nor node version (as per your previous test with using console-ninja.node setting) are the source of the issue. This means that something else in your environment is causing the issue, but unfortunately we can't understand why it happens or how exactly to troubleshoot it. Something is preventing the extension to spawn node process(es), even though both node executable and the entry file are there.

Do you have any firewall/anti virus software installed on the machine? If so, can you please try to temporarily disable it to see if it help to run the tool while it's off?

Also, please check that your PATH environment variable has not been corrupted, and looks as expected (echo $PATH).

@erufenix
Copy link
Author

Ok, I'm going to check my environment

@erufenix
Copy link
Author

erufenix commented May 9, 2024

@erufenix Thanks for providing the extension's archive. We have inspected it and everything looks expected, so neither corrupted extension installation, nor node version (as per your previous test with using console-ninja.node setting) are the source of the issue. This means that something else in your environment is causing the issue, but unfortunately we can't understand why it happens or how exactly to troubleshoot it. Something is preventing the extension to spawn node process(es), even though both node executable and the entry file are there.

Do you have any firewall/anti virus software installed on the machine? If so, can you please try to temporarily disable it to see if it help to run the tool while it's off?

Also, please check that your PATH environment variable has not been corrupted, and looks as expected (echo $PATH).

/Users/edgarhtech/Library/Android/sdk/platform-tools /Users/edgarhtech/Library/Android/sdk /opt/flutter/bin /opt/homebrew/bin /usr/local/bin /System/Cryptexes/App/usr/bin /usr/bin /bin /usr/sbin /sbin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin /var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin /Library/Apple/usr/bin

@j3ang
Copy link

j3ang commented Nov 14, 2024

where node.

Can you please provide us with the zipped contents of your Console Ninja extension directory? If you are using the latest version, it should be located here:

~/.vscode/extensions/wallabyjs.console-ninja-1.0.290

console-ninja_eru.tar.gz

@ArtemGovorov
having same problem here.

15:16:45.297 info extension stopping host
15:16:45.302 ERR! extension host process error: spawn /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) ENOENT
15:17:07.002 info extension stopping host
15:17:07.006 ERR! extension host process error: spawn /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) ENOENT
15:18:34.517 info extension stopping host
15:18:34.521 ERR! extension host process error: spawn /Users/alexw/.nvm/versions/node/v18.20.5/bin/node ENOENT

I added '/Users/alexw/.nvm/versions/node/v18.20.5/bin/node'

but i'm getting

15:18:34.521 ERR! extension host process error: spawn /Users/alexw/.nvm/versions/node/v18.20.5/bin/node ENOENT

and verified node path is correct and working.

>>> /Users/alexw/.nvm/versions/node/v18.20.5/bin/node -v
>>> v18.20.5

@smcenlly
Copy link
Member

@j3ang - can you please describe how you installed VS Code? We've seen some issues where NOT installing VS Code from the official Microsoft download has caused some problems (e.g. when installing using a different package / application manager).

Could you please try uninstalling VS Code and reinstalling the latest version from the VS Code official download?

@j3ang
Copy link

j3ang commented Nov 15, 2024

@smcenlly hmm, I did a fresh re-install. I'm still getting the error.

11:39:45.136 ERR! extension host process error: spawn /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper (Plugin).app/Contents/MacOS/Code Helper (Plugin) ENOENT

@j3ang
Copy link

j3ang commented Nov 15, 2024

so I figured out the problem for my case. My project folder was in an external drive. It sucessfully started after I moved the folder to the laptop.

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

No branches or pull requests

4 participants