We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From stack overflow article: https://stackoverflow.com/questions/69818514/cloud-code-kubernetes-spawn-python-enoent-error-in-vs-code-when-attaching-a-debu
From cloud-code-vscode-internal created by quoctruong: GoogleCloudPlatform/cloud-code-vscode-internal#5848
We are missing a which statement here: https://github.com/GoogleCloudPlatform/cloud-code-vscode-internal/blob/dd72c6c7a13a0d48379f965712597fa29153da23/src/kubernetes/src/debuggers/python_debug_agent.ts#L91
which
Because of this, users can get a cryptic ENOENT spawn Python error.
ENOENT spawn Python
The text was updated successfully, but these errors were encountered:
No branches or pull requests
From stack overflow article: https://stackoverflow.com/questions/69818514/cloud-code-kubernetes-spawn-python-enoent-error-in-vs-code-when-attaching-a-debu
From cloud-code-vscode-internal created by quoctruong: GoogleCloudPlatform/cloud-code-vscode-internal#5848
We are missing a
which
statement here:https://github.com/GoogleCloudPlatform/cloud-code-vscode-internal/blob/dd72c6c7a13a0d48379f965712597fa29153da23/src/kubernetes/src/debuggers/python_debug_agent.ts#L91
Because of this, users can get a cryptic
ENOENT spawn Python
error.The text was updated successfully, but these errors were encountered: