You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When the extension want to install things like gopls, it can't as some places use certifcate chains. This is solved by using -insecure in the go get command. Describe the solution you'd like
I think the issue is in the goGetPackage.ts file. Line 35, I think you need to add '-insecure' after the '-v'. Although this would be better if it was configurable. I don't think everyone would want the default being insecure Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I typicall copy and paste the command it is trying to run in code's terminal and add the -insecure option. Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
If you have a question, please ask it on the
#vscode
or#vscode-go
channels in Gophers Slack](https://invite.slack.golangbridge.org/messages/vscode).Is your feature request related to a problem? Please describe.
When the extension want to install things like gopls, it can't as some places use certifcate chains. This is solved by using -insecure in the go get command.
Describe the solution you'd like
I think the issue is in the goGetPackage.ts file. Line 35, I think you need to add '-insecure' after the '-v'. Although this would be better if it was configurable. I don't think everyone would want the default being insecure
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
I typicall copy and paste the command it is trying to run in code's terminal and add the -insecure option.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: