-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sf org list intermittently prints nothing #2557
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
@kyle-blair - can you please grab a stack trace so I can make this fail in a similar way? I can run |
The full logs have more information than I'm willing to share and redacting is a pain. Let me know if this snippet helps. Looks like it's failing in the node TCP stack. agent-base Resolving socket for 'https:' request: 'GET /services/data/v50.0' +3ms
https-proxy-agent:agent Creating `net.Socket`: { protocol: 'http:', slashes: true, auth: null, host: 'proxy.company.com', port: 80, hostname: 'proxy.company.com', hash: null, search: null, query: null, href: 'http://proxy.company.com/' } +1ms
https-proxy-agent:parse-proxy-response onerror Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -54, code: 'ECONNRESET', syscall: 'read' } +1ms
https-proxy-agent:parse-proxy-response onerror Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -54, code: 'ECONNRESET', syscall: 'read' } +0ms
https-proxy-agent:parse-proxy-response onerror Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -54, code: 'ECONNRESET', syscall: 'read' } +12ms
https-proxy-agent:parse-proxy-response onerror Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -54, code: 'ECONNRESET', syscall: 'read' } +1ms
https-proxy-agent:parse-proxy-response onerror Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -54, code: 'ECONNRESET', syscall: 'read' } +0ms
[11:19:55.497] WARN (sf:connection):
0: "Failed to set the latest API version:"
1: {
"message": "request to https://sandbox.sandbox.my.salesforce.com/services/data failed, reason: read ECONNRESET",
"type": "system",
"errno": "ECONNRESET",
"code": "ECONNRESET"
} |
Thanks for the trace @kyle-blair. I'm going to mark this as a duplicate of #1350 (there was no way for you to know that, but it's the same underlying cause that we need to fix in jsforce) |
Summary
The
sf org list
command frequently (maybe > 50% of the time) prints no output. Other times it works correctly. Looking through the--dev-debug
output shows various network issues such as502 notresolvable
andAdditionally, when the command prints no output and clearly does not run in a successful manner, the exit code is still 0, incorrectly indicating success.
Steps To Reproduce
sf org list
.Expected result
The command always provides output. Output is either the requested list of orgs or an error indicating what went wrong. The return status of the command should be 0 for success and not zero for failure.
Actual result
Some of the time, the command prints nothing. When nothing is printed, the exit code is 0, indicating success.
System Information
The text was updated successfully, but these errors were encountered: