SVT:Start in debug mode for appsody projects throws connection closed errors and port forward errors

[jagraj]

Codewind version: 0.13.0
OS: Windows, CoreOS

Che version:
IDE extension version:
IDE version:
Kubernetes cluster:
OCP 4.3

Description:
During "Restart in debug" mode resulting closed connection error message in popup message and also bunch port forward errors in the console. Looks like we are trying to port forward before pod is up and running.

Steps to reproduce:

1. Install remote codewind.
2. Start appsody open liberty remote project in debug mode.
3. You will see Connection errors dialog and portfarward errors.

Workaround:

[jagraj]

/area eclipse-ide
/priority stopship

[malincoln]

tagging @sishida and @micgibso per slack update from Jag:
"we need doc for the users to set the port forward timeouts other wise they will keep disconnecting from the debugger."

Adding docs label,

[jagraj]

/area vscode-ide

[DavidG1011]

Codewind version: 0.13.0
OS: MacOS

IDE extension version: 0.13
IDE version: VSCode 1.45.1
Kubernetes cluster: OCP 4.2

Also seeing this same/similar issue on VSCode. This was with an Appsody Open Liberty project:

[tetchel]

I'm pretty sure this is the same issue as #239 where the Appsody extension sends the 'project restart success' event before the project is ready #239 (comment)

[sishida]

If this issue 3119 is the same as issue 239 as Tim suggested, here is the existing doc change for issue 239: eclipse-archived/codewind-docs@fd33944

Of course, we can edit or add to this area of the docs as needed. Thanks!

[malincoln]

tagging @sishida and @micgibso per slack update from Jag:
"we need doc for the users to set the port forward timeouts other wise they will keep >disconnecting from the debugger."
tagging @sishida and @micgibso per slack update from Jag:
"we need doc for the users to set the port forward timeouts other wise they will keep >disconnecting from the debugger."

Adding docs label,

Removing doc label. Jag confirmed this one does not need doc changes but 3118.

[jagraj]

This issue has been resolved with the latest plugins and images.