License activate load infinity on MAC mini M1

[erufenix]

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

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]

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]

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]

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]

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]

It is not solved, the problem continues

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

[ArtemGovorov]

@erufenix Can you please run:

> /opt/homebrew/bin/node -v

in your terminal share the output?

[erufenix]

v21.6.2

[smcenlly]

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]

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]

@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]

Ok, I'm going to check my environment

[erufenix]

@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