Help Wanted: Test new networking stack #22214

Activity

1. João Moreno (joaomoreno)

   added

   proxyIssues regarding network proxiesIssues regarding network proxies

   on Mar 8, 2017
2. João Moreno (joaomoreno)

   added this to the March 2017 milestone on Mar 8, 2017
3. João Moreno (joaomoreno)

   self-assigned this

   on Mar 8, 2017
4. leonibr commented on Mar 8, 2017

   

   Ashley Marques (leonibr)

   on Mar 8, 2017 via email

   More actions

   Windows link is dead Em 08/03/2017 08:51, "João Moreno" <notifications@github.com> escreveu:

   …

   If you were pinged to this thread, it's because you helped out in #18103 <#18103>. With #21879 <#21879>, all network communication was moved to the Chrome's network stack. We'll try to fix the proxy issues over that layer, instead of having two layers. The latest Insiders release is already out, please give it a try: - Windows <https://vscode-update.azurewebsites.net/latest/win32-setup/insider> - macOS <https://vscode-update.azurewebsites.net/latest/darwin/insider> - Linux 64 <https://vscode-update.azurewebsites.net/latest/linux-ia32/insider> - Linux 32 <https://vscode-update.azurewebsites.net/latest/linux-x64/insider> Please check whether you can: 1. Browse extensions 2. Install extensions If stuff fails, please open the dev tools (F1, Developer Tools), try again and check the Network tab for failing requests. @dfroze <https://github.com/dfroze> @akcorp2003 <https://github.com/akcorp2003> @fazouane-marouane <https://github.com/fazouane-marouane> @ywmail <https://github.com/ywmail> @abargstaedt <https://github.com/abargstaedt> @liaoya <https://github.com/liaoya> @R3V07T <https://github.com/R3V07T> @hbuckle <https://github.com/hbuckle> @ocean <https://github.com/ocean> @joewood <https://github.com/joewood> @martinmcwhorter <https://github.com/martinmcwhorter> @critesjm <https://github.com/critesjm> @dotalchemy <https://github.com/dotalchemy> @Jule- <https://github.com/Jule-> @diggamies <https://github.com/diggamies> @Efluminor <https://github.com/Efluminor> @egamma <https://github.com/egamma> @the-shank <https://github.com/the-shank> @raphabi <https://github.com/raphabi> @ununseptium <https://github.com/ununseptium> @Platzer <https://github.com/Platzer> @williamchang <https://github.com/williamchang> @rfc791 <https://github.com/rfc791> @iamitava <https://github.com/iamitava> @ramdacxp <https://github.com/ramdacxp> @jrieken <https://github.com/jrieken> @abdinfos <https://github.com/abdinfos> @ericc4 <https://github.com/ericc4> @lcrok <https://github.com/lcrok> @wiz <https://github.com/wiz> @Harpagon <https://github.com/Harpagon> @equinoxel <https://github.com/equinoxel> @sattlt <https://github.com/sattlt> @nassoman <https://github.com/nassoman> @jithurjacob <https://github.com/jithurjacob> @sebastienraillet <https://github.com/sebastienraillet> @rafaelcneves <https://github.com/rafaelcneves> @FloMaetschke <https://github.com/FloMaetschke> @JesusSerranoGL <https://github.com/JesusSerranoGL> @kad <https://github.com/kad> @roblourens <https://github.com/roblourens> @leonibr <https://github.com/leonibr> @eolandezhang <https://github.com/eolandezhang> @xapienz <https://github.com/xapienz> @temurphy <https://github.com/temurphy> @atierant <https://github.com/atierant> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22214>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHjPFWiWCO7Vf94_f6cy_y5AdjVTe8eqks5rjpYngaJpZM4MWsMK> .
5. rafaelcneves commented on Mar 8, 2017

   

   Rafael Neves (rafaelcneves)

   on Mar 8, 2017

   More actions

   The "Linux 32" link is with "Linux 64" url, the same issue with "Linux 64" link
6. fazouane-marouane commented on Mar 8, 2017

   

   Marouane Fazouane (fazouane-marouane)

   on Mar 8, 2017

   Last edited by fazouane-marouane

   More actions

   The link to vscode insider
   https://code.visualstudio.com/insiders

   João Moreno (@joaomoreno) Thanks for the update. I'll test it this afternoon.

   Update
   It works like a charm! 😁
7. xapienz commented on Mar 8, 2017

   

   Evgeny Brazgin (xapienz)

   on Mar 8, 2017

   Last edited by xapienz

   More actions

   Hello João Moreno (@joaomoreno), thank you for your effort.
   I installed latest linux-64 deb from https://code.visualstudio.com/insiders (same build number as in tar.gz here - 1.11.0-1488956710_amd64).

   After the update the problem #18920 didn't disappear, it still persists (net::ERR_INSECURE_RESPONSE in developer console). Moreover, after the update I cannot check for updates using "Help - Check for updates" (menu item disables forever, no messages appear in developer console). In previous version I could check for updates correctly.

   Then I started code-insiders with code-insiders --verbose and noticed the message as in #17360 (ERROR:cert_verify_proc_nss.cc(942)] CERT_PKIXVerifyCert). So the workaround with certutil could help me (though nothing works without applying workaround).

   In short, my problem seems to be not in proxy settings, it is the problem in accepting the corporate certificate despite using http.proxyStrictSSL: false.
8. rafaelcneves commented on Mar 8, 2017

   

   Rafael Neves (rafaelcneves)

   on Mar 8, 2017

   More actions

   I installed the latest version of code-insiders from the ppa, and I've tried with the links above too on linux x64.

   And the error persists, I'm getting net::ERR_CONNECTION_TIMED_OUT in developer console.

   I have sure that proxy is correctly configured because I tried to simulate the same request on Postman and curl and there it works.

   👍React with 👍1Reacted by Laur
9. equinoxel commented on Mar 8, 2017

   

   Laur (equinoxel)

   on Mar 8, 2017

   More actions

   I've installed latest update for windows and I get the same error.
10. FloMaetschke commented on Mar 8, 2017

    

    FloMaetschke

    on Mar 8, 2017

    More actions

    Hi João Moreno (@joaomoreno) jaomoreno!

    I still get the problem with ERR_TUNNEL_CONNECTION_FAILED.

    I am using http_proxy setting in system env which works fine with npm.

    workbench.main.js:142 POST https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery net::ERR_TUNNEL_CONNECTION_FAILED(anonymous function)

    

    workbench.main.js:142 POST https://marketplace.visualstudio.com/_apis/public/gallery/extensionquery net::ERR_TUNNEL_CONNECTION_FAILED(anonymous function) @ workbench.main.js:142n.Class.derive._oncancel @ workbench.main.js:32t.xhrRequest @ workbench.main.js:142e.request @ workbench.main.js:142n.request @ workbench.main.js:142(anonymous function) @ workbench.main.js:142then @ workbench.main.js:32e.queryGallery @ workbench.main.js:142e.query @ workbench.main.js:142e.queryGallery @ workbench.main.js:97t.query @ workbench.main.js:138t.doSearch @ workbench.main.js:138(anonymous function) @ workbench.main.js:138e.queue @ workbench.main.js:32(anonymous function) @ workbench.main.js:32(anonymous function) @ workbench.main.js:32g @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_completed @ workbench.main.js:32(anonymous function) @ workbench.main.js:32
    4workbench.main.js:103 An unknown error occurred. Please consult the log for more details.e.doShow @ workbench.main.js:103e.show @ workbench.main.js:103(anonymous function) @ workbench.main.js:103e.show @ workbench.main.js:103t.onError @ workbench.main.js:138(anonymous function) @ workbench.main.js:138done @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_chainedError @ workbench.main.js:32n @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_error @ workbench.main.js:32(anonymous function) @ workbench.main.js:32done @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_error @ workbench.main.js:32(anonymous function) @ workbench.main.js:32done @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_error @ workbench.main.js:32u @ workbench.main.js:32(anonymous function) @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_chainedError @ workbench.main.js:32n @ workbench.main.js:32then @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_setCompleteValue @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_chainedError @ workbench.main.js:32n @ workbench.main.js:32v @ workbench.main.js:32enter @ workbench.main.js:32_run @ workbench.main.js:32_error @ workbench.main.js:32
    

    👍React with 👍3Reacted by Jule-, Marco Paland and Jacob Cofman
11. FloMaetschke commented on Mar 8, 2017

    

    FloMaetschke

    on Mar 8, 2017

    Last edited by FloMaetschke

    More actions

    João Moreno (@joaomoreno)

    " The proxy settings are automatically picked up from your system's configuration. So, if stuff fails, the first thing you can check if whether your system is correctly configured to use your proxy."

    • What exactly do you mean with this statement:
      HTTP_PROXY enviroment variables?
      Windows Proxy Settings(IE)?

    👍React with 👍1Reacted by Rafael Neves
12. JesusSerranoGL commented on Mar 8, 2017

    

    JesusSerranoGL

    on Mar 8, 2017

    More actions

    Insiders version worked for me! Thanks!

    👍React with 👍1Reacted by João Moreno
13. joaomoreno commented on Mar 8, 2017

    

    João Moreno (joaomoreno)

    on Mar 8, 2017

    ContributorAuthor

    More actions

    Fixed the links, sorry guys. 😨
14. joaomoreno commented on Mar 8, 2017

    

    João Moreno (joaomoreno)

    on Mar 8, 2017

    ContributorAuthor

    More actions

    Evgeny Brazgin (@xapienz) I'm now investigating on how to support the scenario of untrusted certificates. 👍

    Rafael Neves (@rafaelcneves) Strange. Chrome works well in your system? Do you have Firefox? If so, do you manually configure the proxy settings in it?

    FloMaetschke I mean the Windows Proxy Settings(IE). The HTTP_PROXY doesn't work anymore.
15. FloMaetschke commented on Mar 8, 2017

    

    FloMaetschke

    on Mar 8, 2017

    More actions

    João Moreno (@joaomoreno) Proxy Settings are set but not working.
16. 65 remaining items

    Load more

17. martinmcwhorter commented on May 30, 2017

    

    Martin McWhorter (martinmcwhorter)

    on May 30, 2017

    More actions

    I can confirm I am still having this issue trying to access the marketplace through a corporate proxy

    VSCode: 1.12.1
    OS: Windows 7
    Proxy configured through PAC.

    When I try to access recommended extensions I get this in the debug console:

    

    I have deleted all of my proxy config settings from VSCode, exited and restarted VSCode I get the same result.

    If I only delete the first line, and leave in the second line of the config:

    //"http.proxy": "http://<user>:<pass>@<proxyhost>:<port>",
    "http.proxyStrictSSL": false,
    

    It still does not work. I get the same result.
18. akcorp2003 commented on May 31, 2017

    

    Aland Kuang (akcorp2003)

    on May 31, 2017

    Last edited by akcorp2003

    More actions

    Currently on Mac OSX Sierra 10.12.5, VS Code 1.12.2, I am able to search for extensions now, however, the thumbnails do not appear and if I click on "install," I get an error message.

    
19. Benjamin Pasero (bpasero)

    modified the milestones: May 2017, June 2017 on Jun 1, 2017
20. ywmail commented on Jun 9, 2017

    

    Wayne Yang (ywmail)

    on Jun 9, 2017

    More actions

    Please add no.proxy setting support. Some extensions honour vscode's http.proxy setting, but some network requests from these extensions like testing local APIs, should not go through proxy.

    I'm using this extension: REST Client humao.rest-client
    I can send request to github.com, like:

    GET https://github.com/ HTTP/1.1
    content-type: application/json
    

    But I can't send request to local APIs when http.proxy is set.

    GET http://127.0.0.1:18081/api/test / HTTP/1.1
    content-type: application/json
    

    remove the http.proxy setting is OK to send the request.

    👍React with 👍2Reacted by Kevin Kennedy and Max De Wilde
21. HolyGeneralK commented on Jun 14, 2017

    

    Kevin Kennedy (HolyGeneralK)

    on Jun 14, 2017

    More actions

    Seconded on the no.proxy or http.noproxy support (or at least make sure that we can use a system setting). If you'd like me to create a new issue and link it here I can. I would be able to do some limited testing if needed.
22. João Moreno (joaomoreno)

    modified the milestones: Backlog, June 2017 on Jun 27, 2017
23. microsoft

    locked and limited conversation to collaborators on Jul 3, 2017
24. joaomoreno commented on Jul 3, 2017

    

    João Moreno (joaomoreno)

    on Jul 3, 2017

    ContributorAuthor

    More actions

    Thanks for all the help people!
25. microsoft

    unlocked this conversation on Jul 3, 2017
26. microsoft

    locked and limited conversation to collaborators on Jul 3, 2017
27. João Moreno (joaomoreno)

    closed this as completedon Jul 3, 2017