vscode icon indicating copy to clipboard operation
vscode copied to clipboard

Package window installation package keeps timeout

Open wangshunshun opened this issue 7 months ago • 4 comments

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version:
  • OS Version:

Steps to Reproduce:

  1. When packaging the window installation package and consistently exceeding the time limit, an error message appears AbortError: This operation was aborted at new DOMException (node:internal/per_context/domexception:53:5) at AbortController.abort (node:internal/abort_controller:391:18) at Timeout._onTimeout (D:\vscode源码\vscode-wss\vscode\build\lib\fetch.js:47:53) at listOnTimeout (node:internal/timers:581:17)

wangshunshun avatar May 09 '25 08:05 wangshunshun

Where do you see this error? What are you trying to do?

TylerLeonhardt avatar May 09 '25 17:05 TylerLeonhardt

您在哪里看到这个错误?您想做什么? Package window installation package

wangshunshun avatar May 12 '25 01:05 wangshunshun

Where do you see this error? Show me a screenshot.

TylerLeonhardt avatar May 22 '25 20:05 TylerLeonhardt

Where do you see this error? Show me a screenshot.你在哪里看到这个错误?请截图给我看看。

Image

Hust-Why avatar May 23 '25 04:05 Hust-Why

Oh so you are trying to build the vscode server.

I assume that you have all the pre-requisites here:

https://github.com/microsoft/vscode/wiki/How-to-Contribute

@deepak1556 any ideas why building would timeout like this?

TylerLeonhardt avatar May 24 '25 15:05 TylerLeonhardt

The original issue talks about window installation but the error screenshot is from linux remote server, please clarify the issue. Can you access https://nodejs.org/dist/v20.18.3/ ? The timeout is from https://github.com/microsoft/vscode/blob/e806b1ba019c196e7c410cb9d4964f1e0419423b/build/lib/fetch.ts#L53 which hints to be a network error on your end. Couple of things to try,

  1. Run with verbose option by passing it via https://github.com/microsoft/vscode/blob/e806b1ba019c196e7c410cb9d4964f1e0419423b/build/gulpfile.reh.js#L235
  2. Test with main branch which uses Node.js v22.15.0

deepak1556 avatar May 26 '25 09:05 deepak1556

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!