Miguel Núñez Díaz-Montes

Results 15 comments of Miguel Núñez Díaz-Montes

Hi After updating to the latest-rc ```shell $ sfdx --version && sfdx info:releasenotes:display sfdx-cli/7.138.0 wsl-x64 node-v16.13.0 ERROR running info:releasenotes:display: Socket is closed ```

Hello @iowillhoit !! I have both env variables configured ```bash $ echo $HTTPS_PROXY && echo $HTTP_PROXY && sfdx info:releasenotes:display http://**** http://**** ERROR running info:releasenotes:display: Socket is closed ```

@iowillhoit I normally use sfdx + wsl + proxy with no problem, just this command I think. I will try to check other commands and I reach you back. Also,...

I have tried with no proxy issues the following commands ``` sfdx force:source:deploy/retrieve sfdx force:mdapi:deploy/retrieve sfdx force:source:deploy:report sfdx force:user:display sfdx force:schema:sobject:list sfdx force:schema:sobject:describe -s WorkOrder sfdx force:apex:execute -f ./test.apex sfdx...

# Windows Running in windows without VPN (I assusme this is a problem with the antivirus) (normally disabling ssl verification allows me to fetch this, i assume it is impossible...

Appently, the problem is the line 94 of the `dist/hooks/updateReachability.js` Updating the platform from wsl to linux apparently solves the issue ![image](https://user-images.githubusercontent.com/10410852/96554564-fba25600-12b6-11eb-9dc8-ebda1ea8a256.png) Maybe just creating the manifest file for wsl-x64...

Apparently, salesforce recommends installing sfdx as a global package using npm https://developer.salesforce.com/blogs/2018/05/using-salesforce-cli-with-windows-subsystem-for-linux-in-10-easy-steps.html

are you using wsl? this only happens when running in wsl The URL used in the `dist/hooks/updateReachability.js` still points to https://developer.salesforce.com/media/salesforce-cli/sfdx-cli/channels/stable/wsl-x64 which is not available ![image](https://user-images.githubusercontent.com/10410852/99183513-a6822480-273c-11eb-928c-ad8ab7b62407.png) ``` # sfdx --version...