search

microsoft / ripgrep-prebuilt

Builds ripgrep on Azure Pipelines for multiple platforms and makes the binaries available as Github releases
MIT License
46 stars 15 forks source link

Downloading ripgrep failed #17

Closed weartist closed 2 years ago

weartist commented 2 years ago

I'm having some problems with yarn vscode and it looks like it's because I'm using a proxy, do you have any clues?

error /vscode/node_modules/vscode-ripgrep: Command failed. Exit code: 1 Command: node ./lib/postinstall.js Arguments: Directory: /vscode/node_modules/vscode-ripgrep Output: Finding release for v13.0.0-4 GET https://api.github.com/repos/microsoft/ripgrep-prebuilt/releases/tags/v13.0.0-4 Deleting invalid download cache Downloading ripgrep failed: TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"

roblourens commented 2 years ago

Should be fixed in version 1.14.2 of @vscode/ripgrep (just published)

https://github.com/microsoft/vscode-ripgrep/issues/26

weartist commented 2 years ago

Should be fixed in version 1.14.2 of @vscode/ripgrep (just published)

microsoft/vscode-ripgrep#26

thanks!

weartist commented 2 years ago

It doesn't seem to be working for my computer, I still have the same prompt

roblourens commented 2 years ago

Which version of node are you using? Does it work with 14.x? And you have 1.14.2 of the npm module?

weartist commented 2 years ago

Which version of node are you using? Does it work with 14.x? And you have 1.14.2 of the npm module?

node is 16.13.2, Is it possible that the version is too high?

roblourens commented 2 years ago

In microsoft/vscode-ripgrep#26 it was claimed that version of node would have this issue. It should have been fixed but I couldn't repro the issue to confirm.

Are you sure you have 1.14.2 of the npm module?

weartist commented 2 years ago

In microsoft/vscode-ripgrep#26 it was claimed that version of node would have this issue. It should have been fixed but I couldn't repro the issue to confirm.

Are you sure you have 1.14.2 of the npm module?

yes and "https-proxy-agent": "^5.0.0",

roblourens commented 2 years ago

Thanks for checking. I will reopen the original issue.