Upgrade vscode-ripgrep, to solve proxy issue #8171
Labels
dependencies
pull requests that update a dependency file
help wanted
issues meant to be picked up, require help
Comments
|
@Niklas-Dahlquist would you like to prepare a pull-request to resolve the issue? |
vince-fugnitto
added
the
dependencies
1 task
marcdumais-work
added a commit
that referenced
this issue
Jul 31, 2020
Fixes #8171 This will benefit the developres that build our example application behind a firewall, since now `ripgrep` respects environment proxy settings. Extenders can upgrade their own application's `yarn.lock` since this change will not affect them. Signed-off-by: Marc Dumais <[email protected]>
marcdumais-work
added a commit
that referenced
this issue
Jul 31, 2020
Fixes #8171 This will benefit the developres that build our example application behind a firewall, since now `ripgrep` respects environment proxy settings. Extenders can upgrade their own application's `yarn.lock` since this change will not affect them. Signed-off-by: Marc Dumais <[email protected]>
1 task
marcdumais-work
added a commit
that referenced
this issue
Jul 31, 2020
Fixes #8171 This will benefit the developres that build our example application behind a firewall, since now `ripgrep` respects environment proxy settings. Extenders can upgrade their own application's `yarn.lock` since this change will not affect them. Signed-off-by: Marc Dumais <[email protected]>
marcdumais-work
added a commit
that referenced
this issue
Aug 1, 2020
Fixes #8171 This will benefit the developres that build our example application behind a firewall, since now `ripgrep` respects environment proxy settings. Extenders can upgrade their own application's `yarn.lock` since this change will not affect them. Signed-off-by: Marc Dumais <[email protected]>
minyoungyang
pushed a commit
to minyoungyang/theia
that referenced
this issue
Aug 4, 2020
Fixes eclipse-theia#8171 This will benefit the developres that build our example application behind a firewall, since now `ripgrep` respects environment proxy settings. Extenders can upgrade their own application's `yarn.lock` since this change will not affect them. Signed-off-by: Marc Dumais <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description:
Current used version of vscode-ripgrep doesn't handle proxy settings correctly. This is fixed in version 1.8.0. Upgrade yarn.lock file to use this version
vscode-ripgrep@^1.2.4:
version "1.8.0"
resolved "https://registry.yarnpkg.com/vscode-ripgrep/-/vscode-ripgrep-1.8.0.tgz#dfe7c2ae2a2032df8a8108765c2feef73474888a"
integrity sha512-/Q5XtePkTLLi8yplr5ai24pVEymRF62xH9xXrtj35GTaDCJg3zq1s1/L1UqhVbfNDv4OcMBYjyIAt/quEi3d5w==
dependencies:
https-proxy-agent "^4.0.0"
proxy-from-env "^1.1.0"
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: