httpProxy doesn't work

[grosch]

Self-service

• I'd be willing to implement a fix

Describe the bug

The httpProxy element doesn't seem to work. The connection times out when I try to do an install. If I comment that line out and disconnect from my VPN then the install runs. I'm sure the proxy is correct as it's the same one I use for everything else.

To reproduce

I can't really give you a reproduction as it's just putting the line in the .yarnrc.yml file:

httpProxy: "http://my.proxy.com:1234"

Environment

  System:
    OS: Windows 10 10.0.18363
    CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
  Binaries:
    Node: 12.19.0 - ~\AppData\Local\Temp\xfs-8ee7fb80\node.CMD
    Yarn: 3.0.0 - ~\AppData\Local\Temp\xfs-8ee7fb80\yarn.CMD
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
  npmPackages:
    jest: ^27.0.6 => 27.0.6

Additional context

No response

[yarnbot]

Hi! 👋

This issue looks stale, and doesn't feature the reproducible label - which implies that you didn't provide a working reproduction using Sherlock. As a result, it'll be closed in a few days unless a maintainer explicitly vouches for it or you edit your first post to include a formal reproduction (you can use the playground for that).

Note that we require Sherlock reproductions for long-lived issues (rather than standalone git repositories or similar) because we're a small team. Sherlock gives us the ability to check which bugs are still affecting the master branch at any given point, and decreases the amount of code we need to run on our own machines (thus leading to faster bug resolutions). It helps us help you! 😃

If you absolutely cannot reproduce a bug on Sherlock (for example because it's a Windows-only issue), a maintainer will have to manually add the upholded label. Thanks for helping us triaging our repository! 🌟

[richhooper]

Hi @grosch. Are you still getting this issue or do you think the issue still exists? Happy to have a look and try to reproduce and diagnose. I've use Yarn through proxy before and not had an issue but that was in the v1 codebase.

[grosch]

@richhooper I gave up on the newer version of Yarn as too many things just don't play nice with Angular. I went back to yarn 1.