DanielKristofKiss
commented
6 years ago I got the same:
- Atom 1.23.2
- Nuclide 0.275.0
- Client Os: MacOs 10.13.2
- Server Os: Ubuntu 16.04.3
Open VinayakBagaria opened 6 years ago
DanielKristofKiss
commented
6 years ago I got the same:
TheBirdie
commented
6 years ago Same with;
TheBirdie
commented
6 years ago I've got a workaround if anyone is interested:
cd pty && npm install... ... nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty-v0.0.2-node-v59-linux-x64 for me)pty.js/build/Release/pty.node).. or using an old NodeJS version corresponding to the ABI version 51 should work as well (see here https://nodejs.org/en/download/releases/)
tim-soft
commented
6 years ago I'm also hitting this wall! It looks like the remote terminal function relies on a package that doesn't exist.
Error starting process:
Error: Remote Error: Cannot find module '/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty-v0.1.2-node-v59-linux-x64/pty.node'
processing message {
"protocol": "service_framework3_rpc",
"type": "call",
"method": "PtyService/spawn",
"id": 26,
"args": {
"info": {
"terminalType": "xterm-256color",
"environment": [],
"cwd": "/srv/node/my-remote-project"
},
"client": -6
}
}Jumping into node_modules/nuclide-prebuilt-libs/pty/build It seems like these other builds of pty were made just fine?
pty-v0.0.2-node-v57-darwin-x64 pty-v0.1.2-electron-v1.6-win32-x64 pty-v0.1.2-node-v51-darwin-x64
pty-v0.1.0-node-v57-darwin-x64 pty-v0.1.2-electron-v1.7-darwin-x64 pty-v0.1.2-node-v51-linux-x64
pty-v0.1.2-electron-v1.6-darwin-x64 pty-v0.1.2-electron-v1.7-linux-x64 pty-v0.1.2-node-v51-win32-x64
pty-v0.1.2-electron-v1.6-linux-x64 pty-v0.1.2-electron-v1.7-win32-x64
```bash
Error: Cannot find module '/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty-v0.1.2-node-v59-linux-x64/pty.node'
at Function.Module._resolveFilename (module.js:557:15)
at Function.Module._load (module.js:484:25)
at Module.require (module.js:606:17)
at require (/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.
Following @TheBirdie 's advice, I built my own version from source.
# Get pty src
git clone https://github.com/chjj/pty.js.git
cd pty.js/
# Build pty
yarn install
# Make missing dir from error, in my case /pty-v0.1.2-node-v59-linux-x64
mkdir /root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty-v0.1.2-node-v59-linux-x64
# Copy pty build to error dir
cp ./build/Release/pty.node /root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty-v0.1.2-node-v59-linux-x64/pty.node
```bash
$ node-gyp rebuild
[####################--------------] 20/34gyp info it worked if it ends with ok
gyp info using node-gyp@3.6.2
gyp info using node@9.6.1 | linux | x64
gyp info spawn /usr/bin/python2
gyp info spawn args [ '/root/.nvm/versions/node/v9.6.1/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty.js/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/root/.nvm/versions/node/v9.6.1/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/root/.node-gyp/9.6.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/root/.node-gyp/9.6.1',
gyp info spawn args '-Dnode_gyp_dir=/root/.nvm/versions/node/v9.6.1/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/root/.node-gyp/9.6.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty.js',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.' ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/root/.nvm/versions/node/v9.6.1/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/build/pty.js/build'
CXX(target) Release/obj.target/pty/src/unix/pty.o
In file included from ../node_modules/nan/nan.h:190:0,
from ../src/unix/pty.cc:20:
../node_modules/nan/nan_maybe_43_inl.h: In function ‘Nan::Maybe
After all that, the remote terminal seems to be working just fine, despite all of the pty deprecation warnings.
for this package we've only prebuilt binaries for Node versions corresponding to Electron versions corresponding to Atom versions (Phew!) Currently Atom 1.23/1.24 correspond to Node 7.4.0, and Atom 1.25 corresponds to Node 7.9.0, both of which are covered by this package.
If you aren't using a supported version of node, the nuclide prebuilt libs may not contain useable binaries for you.
paulchill
commented
6 years ago is this fixed?
rwatts3
commented
6 years ago having the same issue, and it's been this way for at least a month, just curious if there is a solution.
shrey150
commented
6 years ago I ran "Application: Install Update" from Atom and this error started occurring and I'm having problems with doing the workaround, is there a definitive solution to this?
leoroh
commented
6 years ago same here. Node version is 6.9.1 and atom 1.28
dotku
commented
6 years ago I manually download the pty version from here https://github.com/daviwil/node-pty-prebuilt
then I got error with function:
Error starting process:
Error: Remote Error: Usage: pty.fork(file, args, env, cwd, cols, rows, uid, gid, utf8, onexit) processing message {"protocol":"service_framework3_rpc","type":"call","method":"PtyService/spawn","id":27,"args":{"info":{"terminalType":"xterm-256color","environment":[],"cwd":"/usr/share/nginx/react-es/"},"client":-4}}
"Error: Usage: pty.fork(file, args, env, cwd, cols, rows, uid, gid, utf8, onexit)\n at new UnixTerminal (/home/ec2-user/.nvm/versions/node/v10.11.0/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/lib/unixTerminal.js:53:24)\n at Object.spawn (/home/ec2-user/.nvm/versions/node/v10.11.0/lib/node_modules/nuclide/node_modules/nuclide-prebuilt-libs/pty/lib/index.js:12:12)\n at new PtyImplementation (/home/ec2-user/.nvm/versions/node/v10.11.0/lib/node_modules/nuclide/modules/atom-ide-ui/pkg/atom-ide-terminal/lib/pty-service/PtyService.js:247:42)\n at RpcConnection.spawn (/home/ec2-user/.nvm/versions/node/v10.11.0/lib/node_modules/nuclide/modules/atom-ide-ui/pkg/atom-ide-terminal/lib/pty-service/PtyService.js:120:10)"
Issue and Steps to Reproduce
I am not able to open terminal when connected to a remote server via Nuclide. Although, I can edit the files and those changes do reflect in the remote file.
Try connecting to a remote directory. Select 'New Terminal Here' from the Context Menu. It shows :
Expected Behavior
Terminal should open, which allows remote command line interfacing.
Actual Behavior
See response in the image above. Nuclide installs
pty-v0.0.2-node-v51-linux-x64as a directory in remote environment.Versions
Additional Details
apm ls --installed): ├── MagicPython@1.0.12 ├── ask-stack@2.2.0 ├── autocomplete-clang@0.11.4 ├── build@0.70.0 ├── busy-signal@1.4.3 ├── css-snippets@1.1.0 ├── d3-snippets@1.2.1 ├── emmet@2.4.3 ├── es6-snippets@0.3.0 ├── file-icons@2.1.15 ├── flow-ide@1.9.0 ├── highlight-selected@0.13.1 ├── hyperclick@0.1.5 ├── intentions@1.1.5 ├── javascript-snippets@1.2.1 ├── language-babel@2.81.1 ├── language-graphql@0.9.0 ├── language-haskell@1.17.2 ├── language-ini@1.19.0 ├── language-lua@0.9.11 ├── language-ocaml@1.9.5 ├── language-rust@0.4.12 ├── language-scala@1.1.9 ├── language-swift@0.5.0 ├── language-thrift@1.0.2 ├── linter@2.2.0 (disabled) ├── linter-ui-default@1.6.10 ├── minimap@4.29.7 ├── nuclide@0.273.0 ├── nuclide-format-js@0.0.43 ├── platformio-ide-terminal@2.8.0 ├── prettier-atom@0.45.0 ├── pretty-json@1.6.4 ├── react-native-snippets@0.3.0 ├── react-snippets@1.0.1 ├── scss-snippets@0.6.0 ├── set-syntax@0.4.0 ├── sort-lines@0.18.0 ├── teletype@0.5.0 ├── todo-show@2.1.0 ├── tool-bar@1.1.0 ├── vue-atom-snippets@1.0.0 └── vue-snippets@0.6.0