microsoft / microsoft/vscode-cpptools

yarn install fails bind proxy again

Open
#11,511 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Language Service regression
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Same error as vscode-cpptools/issues/10631, it's said that the problem has been solved by Update vscode/dts #11047, but the bug still exists.

Environment
  • OS and Version: Ubuntu 22.04 6.2.0
  • VS Code Version: 1.83.0
  • C/C++ Extension Version: none
Bug Summary and Steps to Reproduce

Bug Summary:

Steps to reproduce:

git clone https://github.com/Microsoft/vscode-cpptools.git
cd vscode-cpptools/Extension
export https_proxy=http://my_proxy:port
yarn install --proxy http://my_proxy:port

Expected behavior:
install success

Configuration and Logs
yarn install --proxy=http://127.0.0.1:7890
yarn install v1.22.19
[1/5] Validating package.json...
warning cpptools@1.17.5-main: The engine "vscode" appears to be invalid.
[2/5] Resolving packages...
success Already up-to-date.
$ npx vscode-dts dev && npx vscode-dts main
Downloading vscode.proposed.terminalDataWriteEvent.d.ts
To:   /home/wang/Documents/vmm/vscode-cpptools/Extension/vscode.proposed.terminalDataWriteEvent.d.ts
From: https://raw.githubusercontent.com/microsoft/vscode/main/src/vscode-dts/vscode.proposed.terminalDataWriteEvent.d.ts
Read more about proposed API at: https://code.visualstudio.com/api/advanced-topics/using-proposed-api
node:events:492
      throw er; // Unhandled 'error' event
      ^

AggregateError
    at internalConnectMultiple (node:net:1114:18)
    at afterConnectMultiple (node:net:1667:5)
Emitted 'error' event on ClientRequest instance at:
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:514:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'ECONNREFUSED',
  [errors]: [
    Error: connect ECONNREFUSED 0.0.0.0:443
        at createConnectionError (node:net:1634:14)
        at afterConnectMultiple (node:net:1664:40) {
      errno: -111,
      code: 'ECONNREFUSED',
      syscall: 'connect',
      address: '0.0.0.0',
      port: 443
    },
    Error: connect ECONNREFUSED :::443
        at createConnectionError (node:net:1634:14)
        at afterConnectMultiple (node:net:1664:40) {
      errno: -111,
      code: 'ECONNREFUSED',
      syscall: 'connect',
      address: '::',
      port: 443
    }
  ]
}
### Tasks
- [ ] https://github.com/microsoft/vscode-cpptools/issues/10631
- [ ] https://github.com/microsoft/vscode-dts/issues/22

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Extension directory with the reported yarn install --proxy command and inspect the npx vscode-dts dev and main steps shown in the log. Compare the behavior with vscode-cpptools/issues/10631 and vscode-dts/issues/22, then verify that the proposed API files download successfully through the configured proxy.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.