Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to setup vscode locally #13932

Closed
Sujay-shetty opened this issue Oct 18, 2016 · 12 comments
Closed

Unable to setup vscode locally #13932

Sujay-shetty opened this issue Oct 18, 2016 · 12 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@Sujay-shetty
Copy link

Sujay-shetty commented Oct 18, 2016

  • VSCode Version: *
  • OS Version: Windows

Hi,
I'm trying to setup vscode locally in windows 64 bit machine but facing following issue.
I followed the steps in the link https://github.com/Microsoft/vscode/wiki/How-to-Contribute#using-vscode
I can able to install the node modules and also if I run ".\scripts\npm run watch" it is successful without error. When I try to run ".\scripts\code --remote-debugging-port=9222" it is throwing following error.

[16:16:12] Using gulpfile E:\Projects\vscode-master\gulpfile.js
[16:16:12] Starting 'clean-electron'...
[16:16:12] Finished 'clean-electron' after 2.64 ms
[16:16:12] Starting 'electron'...
stream.js:74
      throw er; // Unhandled stream error in pipe.
      ^

Error: unable to verify the first certificate
    at Error (native)
    at TLSSocket.<anonymous> (_tls_wrap.js:1062:38)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:185:7)
    at TLSSocket._finishInit (_tls_wrap.js:586:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:416:38)
The system cannot find the path specified.

@bpasero , @joaomoreno

@roblourens
Copy link
Member

Does it work if you run without the remote-debugging parameter? That's optional, you can also use the builtin chrome devtools to debug.

@roblourens roblourens added the info-needed Issue requires more information from poster label Oct 18, 2016
@Sujay-shetty
Copy link
Author

tried without remote-debugging parameter command (.\scripts\code) but still getting the same error as above.

@roblourens
Copy link
Member

Is there anything weird with your internet connection? A proxy or something? It looks like it's having an issue with downloading electron. You could also try deleting your node_modules folder and running ./scripts/npm install again.

@Sujay-shetty
Copy link
Author

Sujay-shetty commented Oct 19, 2016

@roblourens
Setting up behind corporate proxy.
Tried deleting and installing node packages but did not helped.

@bpasero
Copy link
Member

bpasero commented Oct 19, 2016

No clue, never saw this error.

@roblourens
Copy link
Member

The corporate proxy has got to be the problem. You could check for existing issues at https://github.com/joaomoreno/gulp-atom-electron

@Sujay-shetty
Copy link
Author

@roblourens
Tried the above process to package electron with gulp but still it cannot able to package.

@joaomoreno
Copy link
Member

Try set NODE_TLS_REJECT_UNAUTHORIZED="0" before running .\scripts\code.

@Sujay-shetty
Copy link
Author

@joaomoreno
No luck still stuck in setup.
It is not able to pull electron from git and build the same in corporate proxy.

@joaomoreno
Copy link
Member

Create a folder gulp-electron-cache in your %TEMP%. Place inside electron and ffmpeg and try again.

@Sujay-shetty
Copy link
Author

@joaomoreno
Above link for electron and ffmpeg are hosted on amazon aws servers which are blocked from corporate proxy :(

@joaomoreno
Copy link
Member

We can't really fix your network proxy. :(

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants