-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Node JS (Hello World) iterative debugging fails on the first attempt in iterative development #5914
Comments
@tejal29 - Creating a tracking issue on your side, the iterative debugging on plugins is waiting to be released and waiting on this issue. |
@quoctruong @sivakku Isn't this a dupe of #5704 and fixed with #5804? |
I can't reproduce this on v1.25.0 On every iteration, the breakpoint was hit. See details here. https://github.com/GoogleCloudPlatform/cloud-code-vscode-internal/issues/4671#issuecomment-853327431 @quoctruong mentioned 1:1, there is a connection added in the call stack which is not expected. |
From Chat, hey tejal so i think the flow is like this
However currently it is like this
|
@tejal29 to paste the skaffold actual event stream Vs expected. |
Event stream Before making the change:
If you see, there is a debugging event when a new pod is created. This is because the debug container manager is listening for events with a pod selector. We need to stop the debug container like we do for PortForwarder and then start again at the end of each loop. |
From cloud-code-vscode-internal created by sivakku: GoogleCloudPlatform/cloud-code-vscode-internal#4671
The text was updated successfully, but these errors were encountered: