I tried to use the Alloy analyzer but it crashes as soon as I try to type anything in the editor for example. Any ideas how to fix that ?
It seems as if the problem is only related to the version bundled for Mac. Running the jar from the command line worked.
Related
I'm using Visual Studio Code to (try to) debug my node.js scripts. On the moment I want to debug my index.js file, Visual Studio Code says 'Cannot find runtime 'node' on PATH. Is 'node' installed?
And the answer to this question is 'yes', because it can be found in my 'usr/local/bin' folder. And when I execute the commando 'echo $PATH' in my bash terminal, then I see this path is included (among others):
echo $PATH
/opt/local/bin:/opt/local/sbin:/Users/{myName}/anaconda3/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
Have also done some google searches on the issue but haven't been able to find a sound solution.
Can you please help?
Hans
For background info: I have installed Visual Studio Code via Anaconda and I'm using a Mac on 10.13.6 (MacOS Sierra).
I rather hoped there would be an answer better than the one I am about to give. For me over on Ubuntu 19.04, going through the install process for node fixed the issue; in my case, the PATH variable on my system was correct, and everything in ./.vscode/launch.json was correct. Defeated, I decided to reinstall node, and suddenly debugging worked despite the PATH being exactly the same afterwards. Never thought I would be debugging my debugger!
I wanted to use Visual Studio Code for HaxeFlixel development and the Haxe extension noted that I needed Haxe 3.4.0. I went ahead and downloaded the new installer from the website and installed it on my laptop running Windows 10. However after installing it turned out that calling 'haxelib version' in the command prompt it still returned 3.3.0.
I tried rebooting. Uninstalling then rebooting and installing again. I could find nothing in the system environmental variables that could cause it. Tried updating the Haxe on my Desktop, and had the same issue. Which is running windows 8.1 on it.
Does someone know what might be the cause? Thank you for your time in advance.
To check the Haxe version, use haxe -version. haxelib is a separate application and can have a version number that's different from the compiler's version.
Haxelib 3.3.0 appears to be the version shipped with Haxe 3.4.0-rc.1.
i download Intellij Idea 13 (ideaIC-13.tar.gz) from jetbrains.com and i want to install it on ubuntu 13.10.
i'm not prefer to run intellij with terminal commands everytime i wanna use it, it's gonna be great if i can open it like another applications we install from ubuntu software center.
so i searched over the internet and found out i should compile it to .deb file to do that. i tried several ways to compile but i got error every time.
can anyone help me solve this problem?
thanks in advance
edit :
i tried "Create Desktop Entry" to make shortcut for it, but i got this error.
there is another warning about "native file watcher". how can i solve them?:|
the problem was my Ubuntu installation or lack of my ubuntu dependencies.
now i use Ubuntu 14.04 LTS and Intellij Idea Works Properly! i just run the .sh file with bash command.
and Create Desktop Entry worked fine.
I made the fun decision of upgrading to OS X Mavericks, and now I can't run chromedriver on my machine...
An easy way to replicate this is to create a new project with NodeJS, and install the wd package, then follow their instructions for running tests (this installs selenium and chromedriver).
wd: https://github.com/admc/wd#run-the-tests
I feel like this is settings issue, but am not even sure where to start... Anyone have any ideas?
https://code.google.com/p/chromedriver/issues/detail?id=590
This has been logged. The workaround is to run the chromedriver in verbose mode. Some samples are in the comments there.
Solved thanks to help from sebv, developer of the NodeJS module I mentioned earlier, and located here: https://github.com/admc/wd
Here is the answer to the issue: https://github.com/admc/wd/issues/195
I am completely new to both Macs and Node.js, so sorry if this one is a bit basic.
I am running Mac OS X 10.5 (Leopard) and have just installed the last version of Node.js (released version, not built from source).
Whenever I attempt to run Node or do an NPM install, I get the following error message:
FATAL ERROR: CodeRange::GetNextAllocationBlock Allocation failed - process out of memory
Does anyone know what the problem is? If not, what would be the next steps to figure this out?
Edit: It turns out that if I run these commands a few times then they eventually work. So my work-around is to keep repeating the command until I get success. This is better than nothing but still not acceptable. Software like WebStorm, which needs to execute these tools, doesn't know about this workaround and fails all the time.
The issue seems to show up when running the distributed build of Node on anything pre OSX 10.6.
You can manually build the binary yourself if you don't have the option to upgrade your OS.
http://therobotsbrain.blogspot.com.au/2012/03/installing-nodejs-on-os-x-105.html
I'm running X.5.8, and node 0.10.13 was giving me this error message. I tried some earlier versions of node, and 0.10.3 works while 0.10.4 gets the error message. This is the x86 version, x64 seems to crash at .3 but works at .0. Oh wait, it's more complicated than that. Seems to make a difference when I make a symlink to the app in /usr/local/bin, it crashes. more often. Try a few different ones see which work for you.
I really need to get a new laptop.
download here: http://nodejs.org/dist/