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
Please answer the following before submitting your issue:
See issue eclipse-theia/theia#4590
and other Go debugging related issues on Theia and vscode
You can communicate with everybody who opened these issues directly.
Due to using of non-stable cloud proxies like Traefic which has issues with WS any short-term WS ping-pong frames interchange timeout can cause WS session break by infra. What is your proposals for debug session recovery? If Delve server is deployed to cloud infra and the correct afinity is configured in Proxy server any re-connection attempt from the client side will be useless if server state will be lost. If Delve is deployed on kubernetes pod Delve failure will cause pod re-start but kubernetes doesn't restore container states when re-starting pods.
Unfortunately, DAP protocol spec doesn't contain any recovery sequence.
What version of Delve are you using (dlv version)?
What version of Go are you using? (go version)?
What operating system and processor architecture are you using?
What did you do?
What did you expect to see?
Automatic or manual debug station recovery or restart
What did you see instead?
Debug session freeze
The text was updated successfully, but these errors were encountered:
Please answer the following before submitting your issue:
See issue eclipse-theia/theia#4590
and other Go debugging related issues on Theia and vscode
You can communicate with everybody who opened these issues directly.
Due to using of non-stable cloud proxies like Traefic which has issues with WS any short-term WS ping-pong frames interchange timeout can cause WS session break by infra. What is your proposals for debug session recovery? If Delve server is deployed to cloud infra and the correct afinity is configured in Proxy server any re-connection attempt from the client side will be useless if server state will be lost. If Delve is deployed on kubernetes pod Delve failure will cause pod re-start but kubernetes doesn't restore container states when re-starting pods.
Unfortunately, DAP protocol spec doesn't contain any recovery sequence.
dlv version
)?go version
)?Automatic or manual debug station recovery or restart
Debug session freeze
The text was updated successfully, but these errors were encountered: