swdc-vscode: Extension host crashed

@Ahmeed2m make sure it is updated to latest version.

@kissu we’ll investigate this again, thank you for the trace information.

@Ahmeed2m @HamzaAnis @ronilaukkarinen, thank you for your patience with this issue. It was difficult to reproduce as it seems to throw the mentioned errors in rare cases. We have updated our extension library to ensure we catch these possible TCP conversations abruptly closing, along with the EPIPE error that also shows that a response is trying to pipe to a closed stream. We have deployed v2.2.43 to the marketplace and our team is currently running that version as well to verify the fix. We’d love feedback or any other issue details that can help us understand this more.

Thank you

I don’t want to uninstall this but I am uninstalling it until this bug can not be fixed.

These logs are helpful, thank you. It looks like a new endpoint causing the TCP conversation to abruptly close. I’ll look into this now and provide a response as soon as I can. Thank you for this update.

@brettmstevens7 It still happens in v2.2.38. Just a minute ago it happened. Again the logs if it would help

events.js:180
      throw er; // Unhandled 'error' event
      ^

[Error: Client network socket disconnected before secure TLS connection was established
	at connResetException (internal/errors.js:559:14)
	at TLSSocket.onConnectEnd (_tls_wrap.js:1357:19)
	at Object.onceWrapper (events.js:291:20)
	at TLSSocket.emit (events.js:208:15)
	at endReadableNT (_stream_readable.js:1168:12)
	at processTicksAndRejections (internal/process/task_queues.js:77:11)
Emitted 'error' event at:
	at H.onRequestError (/home/ahmed/.vscode/extensions/softwaredotcom.swdc-vscode-2.2.38/dist/extension.js:462:12993)
	at ClientRequest.emit (events.js:208:15)
	at TLSSocket.socketErrorListener (_http_client.js:399:9)
	at TLSSocket.emit (events.js:203:13)
	at emitErrorNT (internal/streams/destroy.js:91:8)
	at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
	at processTicksAndRejections (internal/process/task_queues.js:77:11)] {
  code: 'ECONNRESET',
  path: null,
  host: 'com-software-prod1.collector.snplow.net',
  port: 443,
  localAddress: undefined,
  vslsStack: [
    CallSite {},
    CallSite {},
    CallSite {},
    CallSite {},
    CallSite {},
    CallSite {}
  ]
}

Sorry about this issue. We ran into some unexpected downtime. The latest version (v2.2.34) was just recently pushed to the marketplace with a fix for this issue.