I am trying to connect to a remote server using Nuclide in Atom.
I'm getting this message error:
"Unable to connect to server:
The server successfully started, but we were unable to connect.
Original error message:
Version mismatch. Client at 217 while server at 216."
It was working well, but then when I updated the nuclide package in Atom I get that error.
I already updated the nuclide server using npm.
Does anyone know how to solve this problem?
I using the Windows 10 system.
Try nuclide-start-server in your server. And check the version in log.
If the version is different in log with your nuclide version,
Try this.
Remove nuclide.
npm remove -g nuclide
npm remove nuclide
Reinstall
npm install -g npm#latest
npm install -g nuclide
And check the version again through nuclide-start-server.
If there is same error after this, check your npm global package directory using npm root -g and see version through nuclide/package.json.
It must has same version with your atom nuclide as "version": "0.218.0".
Normally the default directory is /usr/local/lib/node_modules/nuclide for npm global packages.
Related
I am unable to install firebase tool.
> C:\Users\Mohit Saini>npm i -g firebase-tools
> npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
> npm ERR! Unexpected end of JSON input while parsing near '...ePY2w==","shasum":"89'
firstly run npm cache clean --force to clear previous caches
after that run npm cache verify which will bring 0 bytes indicating all cache was cleared.
lastly run npm install -g firebase-tools
note: running the clean --force command will deletes all data from your cache folder.
When I search for the error message, this Github issue shows up: https://github.com/firebase/firebase-tools/issues/2215, which seems to indicate the problem can be fixed by running:
npm cache verify
If you get problems installing the CLI, and are not familiar enough with the environment to fix them, I'd recommend installing the standalone binary version of the Firebase CLI instead.
I am trying to access an SQLite database from Node-Red. Node-Red is unable to open the DB. My OS is Ubuntu 18.04.3.
My flow and SQLite node definitions are provided below. The inject and debug nodes only have default values. I am keeping it very simple since this is my first attempt at SQLite with Node-Red.
When I deploy my flow, I get the following error:
The db has read-write-execute privileges for all users. It is local on my machine and I am the only one using it.
Any idea what could be causing the issue ?
All right here is how I solved the issue.
I was also having problems opening .csv files. By looking at other similar posts it seemed to be a user privilege problem which could not be resolved, even by changing the file privileges with chmod.
I had installed all the node components using different mediums:
nodejs and npm from the command line
node-red from the Ubuntu Software Center
node-red-dashboard and node-red-node-sqlite from the node-red browser.
These different installation mediums might have caused privilege issues. So I uninstalled everything.
I then reinstalled everything from the command line. Node packages were installed globally (i.e. with "-g" attribute):
sudo apt install nodejs
sudo apt install npm
sudo npm install -g node-red
sudo npm install -g node-red-dashboard
sudo npm install -g node-red-node-sqlite
I then confirmed npm could see everything as global packages:
sudo npm list -g --depth 0
I now launch node-red in a shell:
node-red
Then by going to a browser and typing:
localhost:1880
the node-red browser loads, all dashboard and sqlite nodes are available and I am able to read sqlite & csv files.
*** Note regarding installing node-red sub-packages ***
Node-red sub-packages (node-red-dashboard, node-red-node-sqlite, ...) can be installed from npm or from the node-red browser.
However I noticed a few things:
a sub-package installed from the browser will not show up when typing npm list -g --depth 0.
a sub-package installed with sudo npm -g <sub-package> will show up with npm list -g --depth 0.
packages listed in the browser will not all show up with command npm list <package>.
So I decided to play it safe and install all my node-red sub-packages with npm list. First I search for my sub-package in the node-red browser palett list, I retrieve the sub-package name, then I install it from the shell using sudo npm -g <sub-package>.
Consistency solved the problem: installing everything from the shell as global packages.
Here's the entire error message....
Command 'ASK: Deploy the skill' resulted in an error (ASK CLI v1 is not functional. Command failed: C:\WINDOWS\system32\cmd.exe /q /s /c "ask init -l" error: unknown option '-l' )
Happens when I 'ASK deploy' or any ASK command. Anybody have any ideas what that means?
TIA!!
I figured it out and assuming you are a windows user, this may be your issue.
Before you install ASK-CLI on Windows, you must install the Node.js windows-build-tools package. Before you install windows-build-tools, make sure you have the version of Node.js that the package requires. If you have already installed ASK-CLI you need to uninstall it. Then install it again after you have installed windows-build-tools.
To install windows-build-tools, first open PowerShell with the Run as Administrator option, then type npm install -g --production windows-build-tools.
After I did this, I had to delete and recreate my ASK project, then my ASK deployments started working.
Reference: https://developer.amazon.com/en-US/docs/alexa/smapi/quick-start-alexa-skills-kit-command-line-interface.html
I have a step by step to setup a new environment:
npm install -g --production windows-build-tools
npm install -g ask-cli
ask configure
npm install -g lambda-local
Please assure that you are running the command as Administrator or using sudo on Linux.
I am trying to (re)install Firebase, however, when I run sudo npm install -g firebase-tools the following error shows up:
I have no idea what is wrong, it used to work well a few month ago.
You try running
npm cache clean
and then trying to install again.
If the error is not lost try below
Have you tried installing homebridge with the --unsafe-perm option?
sudo npm install -g --unsafe-perm homebridge
If npm detects it is running as root it drops to a non-privileged user which then doesn't have permissions to write to /root/.node-gyp. The --unsafe-perm option stops it from changing user.
nvm doesn't have this problem when not using sudo because it stores everything under the current users' home directory.
Meteorite installs great (I have to use sudo -H npm install -g meteorite as Meteorite's install instructions recommend), and I can then use it to install standard Meteor packages in my projects, e.g. mrt add jquery. But if I try to install any packages from Atmosphere, e.g. mrt add router or mrt add font-awesome, I get this output:
Installing Meteor
branch: https://github.com/meteor/meteor.git#master
Installing smart packages
/usr/local/lib/node_modules/meteorite/node_modules/ddp/node_modules/ws/lib/WebSocket.js:175
else throw new Error('not opened');
^
Error: not opened
at WebSocket.send (/usr/local/lib/node_modules/meteorite/node_modules/ddp/node_modules/ws/lib/WebSocket.js:175:16)
at DDPClient._send (/usr/local/lib/node_modules/meteorite/node_modules/ddp/lib/ddp-client.js:77:15)
at WebSocket.<anonymous> (/usr/local/lib/node_modules/meteorite/node_modules/ddp/lib/ddp-client.js:49:10)
at WebSocket.EventEmitter.emit (events.js:92:17)
at WebSocket.establishConnection (/usr/local/lib/node_modules/meteorite/node_modules/ddp/node_modules/ws/lib/WebSocket.js:576:8)
at ClientRequest.<anonymous> (/usr/local/lib/node_modules/meteorite/node_modules/ddp/node_modules/ws/lib/WebSocket.js:488:25)
at ClientRequest.g (events.js:175:14)
at ClientRequest.EventEmitter.emit (events.js:106:17)
at CleartextStream.socketOnData (http.js:1587:11)
at CleartextStream.read [as _read] (tls.js:477:10)
mrt run works properly though! I'm on Meteor v0.6.3.1 and Meteorite v0.5.1. Would appreciate any ideas, thanks!
Check your node version.
As of today (May 26, 2013), I can replicate this error perfectly (I get the same error message) when I use node v0.10.8.
However, with node node-v0.9.9 the mrt add command works.
The other parts of my environment are:
Ubuntu 12.04 LTS x64
mrt --version
Meteorite version 0.5.1
This is an issue specifically with Node 0.10.8
https://github.com/oortcloud/meteorite/issues/135
I was able to fix the issue by first removing node using these instructions. One exception is I had issues using nvm to install node so I used a package instead:
How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
You'll find links to download installer package for the 0.10.7 version of node for all os' here:
http://blog.nodejs.org/2013/05/17/node-v0-10-7-stable/
After the install do a node -v to check the version. If it doesn't look right try a restart. I had to reboot in order to get mine happy for some reason.
If you continue to have issues after reinstalling node then try removing and reinstalling meteorite and meteor. Hope this helps someone having the same issue.