Error running build from source - Githubissues

microsoft / vscode

Visual Studio Code

https://code.visualstudio.com

MIT License

162.93k stars 28.77k forks source link

Error running build from source #13275

Closed alefragnani closed 7 years ago

alefragnani commented 7 years ago

VSCode Version: code-oss-dev@1.6.0 (source from Oct 4th)
OS Version: Windows 10 32bits OR 64bits (two different computers - same error)

Steps to Reproduce:

[X] Following How to Contribute
[X] Install Prerequisites 👍
- [X] Node v6.3.1
- [X] NPM 3.10.8
- [X] Python 2.7.11
- [X] Visual Studio 2015 Community with C++
[X] Install dependencies: scripts\npm install 👍
[X] Incremental Build: [23:17:22] Finished compilation with 0 errors after 18584 ms 👍
[ ] Launch development version -> 👎 Error below

C:\Users\alefr\Documents\GitHub\vscode>scripts\code.bat  --verbose

[93m[main 11:32:15 PM][0m Starting VS Code in verbose mode
[93m[main 11:32:15 PM][0m from: c:\Users\alefr\Documents\GitHub\vscode
[93m[main 11:32:15 PM][0m args: { _: [],
  paths: [],
  performance: false,
  verbose: true,
  debugPluginHost: undefined,
  debugBrkPluginHost: undefined,
  logExtensionHostCommunication: false,
  'new-window': false,
  'reuse-window': false,
  goto: false,
  diff: false,
  extensionHomePath: undefined,
  extensionDevelopmentPath: undefined,
  extensionTestsPath: undefined,
  'disable-extensions': false,
  'open-url': undefined,
  locale: undefined,
  wait: false }
[9704:1005/233219:INFO:CONSOLE(136)] "Loading "gc-signals" failed", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (136)
[9704:1005/233219:INFO:CONSOLE(137)] "Detail: ", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (137)
[9704:1005/233219:INFO:CONSOLE(139)] "Error: Cannot find module '../build/Release/gcsignals'
    at Module._resolveFilename (module.js:455:15)
    at Function.Module._resolveFilename (C:\Users\alefr\Documents\GitHub\vscode\.build\electron\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\alefr\Documents\GitHub\vscode\node_modules\gc-signals\src\index.js:8:18)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (139)
[9704:1005/233219:INFO:CONSOLE(141)] "Here are the modules that depend on it:", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (141)
[9704:1005/233219:INFO:CONSOLE(142)] "vs/workbench/api/node/mainThreadLanguageFeatures,vs/workbench/api/node/mainThreadHeapService", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (142)

The OSS Build runs, but open an empty window. No menu item works, except Help/About, Help/Toggle Developer Tools, File/New Window and File/Close, as you can see in the GIF below.

build_oss_gcsignals

Any idea what could be happening? Any missing/invalid pre-requisite? I'm trying to build for about two weeks, and I'm stuck with the same error. I constantly update my sources from GitHub, so it doesn't appears to be a failed changeset

Thanks in advance

joaomoreno commented 7 years ago

@jrieken Something wrong with gc-signals

jrieken commented 7 years ago

@alefragnani Can you attach the output when running ./scripts/npm i please? The gc-signals module is a native module that needs to be compiled using VS

xconverge commented 7 years ago

@jrieken I am having the exact same issue here on win10 x64.

If this is not the exact same thing I will remove the comment and move it elsewhere but I think it is the same issue and I figure a stack trace and answering the questions for you may be helpful in getting this resolved...

VS Community 2015 with c++ and win sdk Python 2.7.12 npm 3.10.8 node 6.7.0

E:\Github\vscode\scripts>code.bat --verbose
[22:22:16] Using gulpfile E:\Github\vscode\gulpfile.js
[22:22:16] Starting 'clean-electron'...
[22:22:16] Finished 'clean-electron' after 1.94 ms
[22:22:16] Starting 'electron'...
↓ ffmpeg-v1.3.7-win32-ia32.zip [====================] 100%
↓ electron-v1.3.7-win32-ia32.zip [====================] 100%
[22:22:23] Finished 'electron' after 7.34 s

{ Error: ENOENT: no such file or directory, open 'C:\Users\sean\AppData\Roaming\code-oss-dev\storage.json'
    at Error (native)
    at Object.fs.openSync (original-fs.js:640:18)
    at Object.fs.readFileSync (original-fs.js:508:33)
    at StorageService.load (E:\Github\vscode\out\vs\code\electron-main\storage.js:57:38)
    at StorageService.getItem (E:\Github\vscode\out\vs\code\electron-main\storage.js:25:38)
    at LifecycleService.handleUpdated (E:\Github\vscode\out\vs\code\electron-main\lifecycle.js:33:54)
    at new LifecycleService (E:\Github\vscode\out\vs\code\electron-main\lifecycle.js:30:18)
    at create (E:\Github\vscode\out\vs\base\common\types.js:163:14)
    at InstantiationService._createInstance (E:\Github\vscode\out\vs\platform\instantiation\common\instantiationService.js:141:43)
    at InstantiationService._createAndCacheServiceInstance (E:\Github\vscode\out\vs\platform\instantiation\common\instantiationService.js:200:41)
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'C:\\Users\\sean\\AppData\\Roaming\\code-oss-dev\\storage.json' }
[93m[main 10:22:24 PM][0m Starting VS Code in verbose mode
[93m[main 10:22:24 PM][0m from: e:\Github\vscode
[93m[main 10:22:24 PM][0m args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'reuse-window': false,
  r: false,
  performance: false,
  p: false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false }
[372:1008/222225:INFO:CONSOLE(136)] "Loading "gc-signals" failed", source: file:///E:/Github/vscode/out/vs/loader.js (136)
[372:1008/222225:INFO:CONSOLE(137)] "Detail: ", source: file:///E:/Github/vscode/out/vs/loader.js (137)
[372:1008/222225:INFO:CONSOLE(139)] "Error: Cannot find module '../build/Release/gcsignals'
    at Module._resolveFilename (module.js:455:15)
    at Function.Module._resolveFilename (E:\Github\vscode\.build\electron\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (E:\Github\vscode\node_modules\gc-signals\src\index.js:8:18)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)", source: file:///E:/Github/vscode/out/vs/loader.js (139)
[372:1008/222225:INFO:CONSOLE(141)] "Here are the modules that depend on it:", source: file:///E:/Github/vscode/out/vs/loader.js (141)
[372:1008/222225:INFO:CONSOLE(142)] "vs/workbench/api/node/mainThreadLanguageFeatures,vs/workbench/api/node/mainThreadHeapService", source: file:///E:/Github/vscode/out/vs/loader.js (142)
[372:1008/222226:INFO:CONSOLE(74)] "Ctrl+Alt+ keybindings should not be used by default under Windows. Offender: ", source: file:///E:/Github/vscode/out/vs/platform/keybinding/common/keybindingsRegistry.js (74)

The output you asked for.

E:\Github\vscode>scripts\npm.bat i
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.2.12: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade

> code-oss-dev@1.7.0 preinstall E:\Github\vscode
> node build/npm/preinstall.js

> code-oss-dev@1.7.0 postinstall E:\Github\vscode
> node build/npm/postinstall.js

> vscode-api-tests@0.0.1 postinstall E:\Github\vscode\extensions\vscode-api-tests
> node ./node_modules/vscode/bin/install

Detected VS Code engine version: *
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/master/src/vs/vscode.d.ts
vscode.d.ts successfully installed!

> vscode-colorize-tests@0.0.1 postinstall E:\Github\vscode\extensions\vscode-colorize-tests
> node ./node_modules/vscode/bin/install

Detected VS Code engine version: *
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/master/src/vs/vscode.d.ts
vscode.d.ts successfully installed!

> json@0.1.0 postinstall E:\Github\vscode\extensions\json
> cd server && npm install

npm WARN vscode-json-languageserver@1.0.0 No repository field.
npm WARN json@0.1.0 No description
npm WARN json@0.1.0 No repository field.
npm WARN json@0.1.0 No license field.
npm WARN configuration-editing@0.0.1 No description
npm WARN configuration-editing@0.0.1 No repository field.
npm WARN configuration-editing@0.0.1 No license field.

> extension-editing@0.0.1 postinstall E:\Github\vscode\extensions\extension-editing
> node ./postinstall

npm WARN extension-editing@0.0.1 No description
npm WARN extension-editing@0.0.1 No repository field.
npm WARN extension-editing@0.0.1 No license field.
npm WARN vscode-markdown@0.2.0 No repository field.
npm WARN vscode-markdown@0.2.0 No license field.
npm WARN typescript@0.10.1 No repository field.
npm WARN php@0.1.0 No description
npm WARN php@0.1.0 No repository field.
npm WARN php@0.1.0 No license field.
npm WARN javascript@0.1.0 No description
npm WARN javascript@0.1.0 No repository field.
npm WARN javascript@0.1.0 No license field.

> css@0.1.0 postinstall E:\Github\vscode\extensions\css
> cd server && npm install

npm WARN vscode-css-languageserver@1.0.0 No repository field.
npm WARN css@0.1.0 No description
npm WARN css@0.1.0 No repository field.
npm WARN css@0.1.0 No license field.

> html@0.1.0 postinstall E:\Github\vscode\extensions\html
> cd server && npm install

npm WARN vscode-html-languageserver@1.0.0 No repository field.
npm WARN html@0.1.0 No description
npm WARN html@0.1.0 No repository field.
npm WARN html@0.1.0 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@github:bpasero/fsevents#vscode (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

E:\Github\vscode>

alefragnani commented 7 years ago

@jrieken the output is here.

C:\Users\alefr\Documents\GitHub\vscode>scripts\npm i
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.2.12: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade

> code-oss-dev@1.6.0 preinstall C:\Users\alefr\Documents\GitHub\vscode
> node build/npm/preinstall.js

> code-oss-dev@1.6.0 postinstall C:\Users\alefr\Documents\GitHub\vscode
> node build/npm/postinstall.js

> vscode-api-tests@0.0.1 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\vscode-api-tests
> node ./node_modules/vscode/bin/install

Detected VS Code engine version: *
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/master/src/vs/vscode.d.ts
vscode.d.ts successfully installed!

> vscode-colorize-tests@0.0.1 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\vscode-colorize-tests
> node ./node_modules/vscode/bin/install

Detected VS Code engine version: *
Fetching vscode.d.ts from: https://raw.githubusercontent.com/Microsoft/vscode/master/src/vs/vscode.d.ts
vscode.d.ts successfully installed!

> json@0.1.0 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\json
> cd server && npm install

npm WARN vscode-json-languageserver@1.0.0 No repository field.
npm WARN json@0.1.0 No description
npm WARN json@0.1.0 No repository field.
npm WARN json@0.1.0 No license field.
npm WARN configuration-editing@0.0.1 No description
npm WARN configuration-editing@0.0.1 No repository field.
npm WARN configuration-editing@0.0.1 No license field.

> extension-editing@0.0.1 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\extension-editing
> node ./postinstall

npm WARN extension-editing@0.0.1 No description
npm WARN extension-editing@0.0.1 No repository field.
npm WARN extension-editing@0.0.1 No license field.
npm WARN vscode-markdown@0.2.0 No repository field.
npm WARN vscode-markdown@0.2.0 No license field.
npm WARN typescript@0.10.1 No repository field.
npm WARN php@0.1.0 No description
npm WARN php@0.1.0 No repository field.
npm WARN php@0.1.0 No license field.
npm WARN javascript@0.1.0 No description
npm WARN javascript@0.1.0 No repository field.
npm WARN javascript@0.1.0 No license field.

> css@0.1.0 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\css
> cd server && npm install

npm WARN vscode-css-languageserver@1.0.0 No repository field.
npm WARN css@0.1.0 No description
npm WARN css@0.1.0 No repository field.
npm WARN css@0.1.0 No license field.

> html@0.1.0 postinstall C:\Users\alefr\Documents\GitHub\vscode\extensions\html
> cd server && npm install

npm WARN vscode-html-languageserver@1.0.0 No repository field.
npm WARN html@0.1.0 No description
npm WARN html@0.1.0 No repository field.
npm WARN html@0.1.0 No license field.
code-oss-dev@1.6.0 C:\Users\alefr\Documents\GitHub\vscode
+-- eslint@3.7.1
| +-- file-entry-cache@2.0.0
| | `-- flat-cache@1.2.1
| |   `-- del@2.2.2
| |     `-- globby@5.0.0
| |       `-- glob@7.1.1
| +-- glob@7.1.1
| `-- lodash@4.16.4
+-- gulp-cssnano@2.1.2
| `-- cssnano@3.7.6
|   `-- autoprefixer@6.5.0
|     `-- caniuse-db@1.0.30000548
+-- rimraf@2.5.4
| `-- glob@7.1.1
`-- tslint@3.15.1
  `-- glob@7.1.1

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.3.8

This output is from a branch cloned directly from Microsoft/vscode. If I run it from my fork (which is a bit older - Sep/29) the log is a bit verbose, but also present the same npm WARN messages at the end, Very similar to @xconverge.

npm WARN vscode-html-languageserver@1.0.0 No repository field.
npm WARN html@0.1.0 No description
npm WARN html@0.1.0 No repository field.
npm WARN html@0.1.0 No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@github:bpasero/fsevents#vscode (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})

Thanks for your help

jrieken commented 7 years ago

Weird - I am expecting a lot more output from node-gyp such as our build machine produce: https://ci.appveyor.com/project/VSCode/vscode/build/1.0.9109#L534. Can clear your node_modules folders first and/or npm i --force install - you should really see something like this in the output

alefragnani commented 7 years ago

Sure, it seems similar. At least that part of the log. Even the error before that also occurs in your build:

I attached the log, because when I tried to paste, the browser stopped working.

build_oss_gcsignals_LOG_SCRIPTS_NPMI--FORCE - 2.txt

But something different occurred. Now the error that appears when I run Code OSS differs. But it also does nothing at all 😢

C:\Users\alefr\Documents\GitHub\vscode>scripts\code.bat

[7828:1011/000826:INFO:CONSOLE(136)] "Loading "gc-signals" failed", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (136)
[7828:1011/000826:INFO:CONSOLE(137)] "Detail: ", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (137)
[7828:1011/000826:INFO:CONSOLE(139)] "Error: A dynamic link library (DLL) initialization routine failed.
\\?\C:\Users\alefr\Documents\GitHub\vscode\node_modules\gc-signals\build\Release\gcsignals.node
    at Error (native)
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:168:20)
    at Object.Module._extensions..node (module.js:583:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:168:20)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\alefr\Documents\GitHub\vscode\node_modules\gc-signals\src\index.js:8:18)", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (139)
[7828:1011/000826:INFO:CONSOLE(141)] "Here are the modules that depend on it:", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (141)
[7828:1011/000826:INFO:CONSOLE(142)] "vs/workbench/api/node/mainThreadLanguageFeatures,vs/workbench/api/node/mainThreadHeapService", source: file:///C:/Users/alefr/Documents/GitHub/vscode/out/vs/loader.js (142)

Thanks for your help.

joaomoreno commented 7 years ago

Please use .\scripts\npm.bat install instead of npm install. More info.

jrieken commented 7 years ago

@joaomoreno they do

joaomoreno commented 7 years ago

The first line of @alefragnani's log is:

C:\Users\alefr\Documents\GitHub\vscode>npm i --force

jrieken commented 7 years ago

I looking at this: https://github.com/Microsoft/vscode/issues/13275#issuecomment-252492642

alefragnani commented 7 years ago

Hi,

I decide to re-clone the repo to try it from scratch.

When I run scripts\npm install, that same Unsupported Platform warning appears, but also an error, asking me to Run As Administrator

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode>scripts\npm install
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.2.12: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.

> code-oss-dev@1.7.0 preinstall C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode
> node build/npm/preinstall.js

code-oss-dev@1.7.0 C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode
+-- agent-base@1.0.2
+-- anymatch@1.3.0
+-- applicationinsights@0.15.6
+-- arr-diff@2.0.0
.........
+-- winreg@1.2.0
+-- xterm@2.0.1  (git+https://github.com/Tyriar/xterm.js.git#2de6617cf1b1d3bb22fdbf284488286a0cc98dcd)
`-- yauzl@2.3.1

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@github:bpasero/fsevents#vscode (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@0.3.8 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\alefr\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.3.1
npm ERR! npm  v3.10.8
npm ERR! path C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\node_modules\.staging\util-deprecate-e2893b47\package.json.1441289573
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall rename

npm ERR! Error: EPERM: operation not permitted, rename 'C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\node_modules\.staging\util-deprecate-e2893b47\package.json.1441289573' -> 'C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\node_modules\.staging\util-deprecate-e2893b47\package.json'
npm ERR!     at Error (native)
npm ERR!  { Error: EPERM: operation not permitted, rename 'C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\node_modules\.staging\util-deprecate-e2893b47\package.json.1441289573' -> 'C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\node_modules\.staging\util-deprecate-e2893b47\package.json'
npm ERR!     at Error (native)
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'rename',
npm ERR!   path: 'C:\\Users\\alefr\\Documents\\GitHub\\GitHub-Testing\\vscode\\node_modules\\.staging\\util-deprecate-e2893b47\\package.json.1441289573',
npm ERR!   dest: 'C:\\Users\\alefr\\Documents\\GitHub\\GitHub-Testing\\vscode\\node_modules\\.staging\\util-deprecate-e2893b47\\package.json',
npm ERR!   parent: 'code-oss-dev' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode\npm-debug.log

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode>

I started CMD as administrator, re-cloned and re-run scripts\npm install, but another error appeared. This time, it didn't try to rename anything (the reason it asked for Administrator), but instead, something related to node-gyp I guess, which it tried to build right at the beginning of the script. Is Run as Administrator really necessary?

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm>scripts\npm install
O sistema não pode encontrar o caminho especificado.

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm>cd vscode

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode>scripts\npm install
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.2.12: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated lodash@1.0.2: lodash@<3.0.0 is no longer maintained. Upgrade to lodash@^4.0.0.

> typechecker@2.0.8 preinstall C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\node_modules\.staging\typechecker-397221a8
> node ./cyclic.js

npm WARN prefer global coffee-script@1.11.1 should be installed with -g
npm WARN prefer global js-beautify@1.5.10 should be installed with -g

> oniguruma@6.1.1 install C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\node_modules\oniguruma
> node-gyp rebuild

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\node_modules\oniguruma>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
  regcomp.c
  regenc.c
  regerror.c
  regexec.c
  regext.c
  reggnu.c
  regparse.c
  regposerr.c
  regposix.c
  regsyntax.c
  regtrav.c
  regversion.c
  st.c
  ascii.c
  big5.c
  cp1251.c
  euc_jp.c
  euc_kr.c
  euc_tw.c
  gb18030.c
  iso8859_1.c
  iso8859_2.c
  iso8859_3.c
  iso8859_4.c
  iso8859_5.c
  iso8859_6.c
  iso8859_7.c
  iso8859_8.c
  iso8859_9.c
  iso8859_10.c
  iso8859_11.c
  iso8859_13.c
  iso8859_14.c
  iso8859_15.c
  iso8859_16.c
  koi8.c
  koi8_r.c
  mktable.c
  sjis.c
  unicode.c
  utf16_be.c
  utf16_le.c
  utf32_be.c
  utf32_le.c
  utf8.c
  win_delay_load_hook.c
C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\src\win_delay_load_hook.c(34): error C2373: '__pfnDliNot
ifyHook2': redefinition; different type modifiers [C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\nod
e_modules\oniguruma\build\oniguruma.vcxproj]
  C:\Program Files\Microsoft Visual Studio 14.0\VC\include\delayimp.h(134): note: see declaration of '__pfnDliNotifyHoo
  k2'
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files\MSBuild\14.0\bin\msbuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\node_modules\oniguruma
gyp ERR! node -v v6.3.1
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok
code-oss-dev@1.7.0 C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode
+-- agent-base@1.0.2
+-- anymatch@1.3.0
+-- applicationinsights@0.15.6
+-- arr-diff@2.0.0
+-- arr-flatten@1.0.1
........
+-- winreg@1.2.0
+-- xterm@2.0.1  (git+https://github.com/Tyriar/xterm.js.git#2de6617cf1b1d3bb22fdbf284488286a0cc98dcd)
`-- yauzl@2.3.1

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.3.8
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v6.3.1
npm ERR! npm  v3.10.3
npm ERR! code ELIFECYCLE

npm ERR! oniguruma@6.1.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the oniguruma@6.1.1 install script 'node-gyp rebuild'.
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 oniguruma package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs oniguruma
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls oniguruma
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode\npm-debug.log

C:\Users\alefr\Documents\GitHub\GitHub-Testing\vscode_adm\vscode>

Thanks for your help.

joaomoreno commented 7 years ago

Strange that you got this from a scratch repo. I'm not sure where C:\\Users\\alefr\\Documents\\GitHub\\GitHub-Testing\\vscode\\node_modules\\.staging comes from... but that is what is causing the issue. Maybe check npm/npm#12540.

Then, for some reason, when you ran as admin, npm 3.10.3 was used... and that's why it broke with the __pfnDliNotifyHook2 error. You really need npm 3.10.8.

In conclusion: never, ever, run npm as an Administrator; make sure you can run normally as your user.

alefragnani commented 7 years ago

@joaomoreno @jrieken I re-cloned the repo and now it's working 🎉 . Even debug is working 😄 .

But, right at the start, with no folder opened (first run or new window), it shows an error related to a core extension. If I open a folder, no problem appears.

build_oss_core_extension_error

I don't know the reason why its working now, since I did everything just like before, with the same tools 🤔 . To be precise, the clone was made at this commit -> Wed Oct 12 12:25:43 2016 -0700.

I still have the clone from Oct 04 and will try to compare them, trying to find out where is the problem, if any.

Thanks for your help

joaomoreno commented 7 years ago

Closing as fixed.

The joaomoreno.git issue is fixed now.

l2dy commented 7 years ago

@alefragnani use git clean -dfx next time.

jschraub commented 7 years ago

Just to note, I came across this same issue. I was able to fix it by git clean -dfx and then rebuilding.