Raspberry issue during npm run watch (gulp watch --max_old_space_size=4096)

[40tude]

• VSCode Version: git fetch from today. (1.11.0)
• OS Version: Linux raspberrypi3 4.4.50-v7+ Proposal for separating the vscode tools from the vscode API #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux

Steps to Reproduce:

1. git fetch origin
2. cd vscode
3. sudo ./scripts/npm.sh install
4. sudo npm run watch

Please find below the output in the console and the content of npm-debug.log
Any help and advises are welcome
Best regards, Philippe

PS : similar behavior if step 3 above is
3. sudo ./scripts/npm.sh install -arch=armhf

// --------------------------------------------------------------
// --------------------------------------------------------------
// --------------------------------------------------------------

[email protected] watch /home/philippe/Documents/vscode
gulp watch --max_old_space_size=4096

[23:01:33] Node flags detected: --max_old_space_size=4096
[23:01:33] Respawned to PID: 5894
Segmentation fault

npm ERR! Linux 4.4.50-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "watch"
npm ERR! node v7.7.1
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! [email protected] watch: gulp watch --max_old_space_size=4096
npm ERR! Exit status 139
npm ERR!
npm ERR! Failed at the [email protected] watch script 'gulp watch --max_old_space_size=4096'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the code-oss-dev package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp watch --max_old_space_size=4096
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs code-oss-dev
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls code-oss-dev
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/philippe/Documents/vscode/npm-debug.log

// --------------------------------------------------------------
// --------------------------------------------------------------
// --------------------------------------------------------------
Content of npm-debug-log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'watch' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prewatch', 'watch', 'postwatch' ]
5 info lifecycle [email protected]prewatch: [email protected]
6 silly lifecycle [email protected]prewatch: no script for prewatch, continuing
7 info lifecycle [email protected]watch: [email protected]
8 verbose lifecycle [email protected]watch: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]watch: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/philippe/Documents/vscode/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle [email protected]watch: CWD: /home/philippe/Documents/vscode
11 silly lifecycle [email protected]watch: Args: [ '-c', 'gulp watch --max_old_space_size=4096' ]
12 silly lifecycle [email protected]watch: Returned: code: 139 signal: null
13 info lifecycle [email protected]~watch: Failed to exec watch script
14 verbose stack Error: [email protected] watch: gulp watch --max_old_space_size=4096
14 verbose stack Exit status 139
14 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:194:7)
14 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:194:7)
14 verbose stack at maybeClose (internal/child_process.js:899:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/philippe/Documents/vscode
17 error Linux 4.4.50-v7+
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "watch"
19 error node v7.7.1
20 error npm v4.1.2
21 error code ELIFECYCLE
22 error [email protected] watch: gulp watch --max_old_space_size=4096
22 error Exit status 139
23 error Failed at the [email protected] watch script 'gulp watch --max_old_space_size=4096'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the code-oss-dev package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error gulp watch --max_old_space_size=4096
23 error You can get information on how to open an issue for this project with:
23 error npm bugs code-oss-dev
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls code-oss-dev
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

[joaomoreno]

Can you retry everything all over again without using sudo at all?

[40tude]

Bonjour Worked like a charm This is all my fault Just to make sure you know what I did wrong : it was an issue of ownership of the directory It is a shame... Sorry for that. One quick question : What is the purpose of "*npm run watch*" and when one is suppose to use it? I saw few words about it in the documentation but the reason why one have to invoque it is not clear for me Thank for your reply You can close the "issue" Thank you again and best regards, Philippe Cordialement, Philippe // ------------------- 40tude.fr 2017-03-09 9:38 GMT+01:00 João Moreno <[email protected]>:

…

Can you retry everything all over again without using sudo at all? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22256 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABbmjWRn4TZTA7H4h364EMDZTSfmtstCks5rj7qZgaJpZM4MXY8C> .

[joaomoreno]

npm run watch compiles our TypeScript sources into JavaScript, which is what gets executed.