Check on debug launch configuration's `python` field prevents container debugging
Nadie ha tomado este issue todavía.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
The Docker extension resolves a Python debug configuration in order to support Python debugging. Included in that resolved debug configuration is the python field, with a value of just python3. This is because this is the command to use for launching Python in the container. However, validation of that field is done against the host, so if the host and container don't both have python3, debugging fails. We've tried changing it to python, which worked on Windows, but failed on Mac and Linux.
Is there a way to override this check to stop it from validating against the host when it should not be?
An additional strange thing we've noticed is that the error seems to only show up on Insiders. The code doesn't seem to be Insiders only so it's confusing why it would be doing this.
- Lenguaje dominante
- TypeScript
- Estrellas
- 181
- Forks
- 126
- Merge medio
- 8 h 49 min
- PR fusionados (30 d)
- 1
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/vscode-python-debugger
-
triage-needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
microsoft/vscode-python-debugger#1110 ·
-
triage-needed
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
microsoft/vscode-python-debugger#1024 · 1 comentario ·
-
triage-needed
microsoft/vscode-python-debugger#1111 · 1 reacción · 1 asignado ·
-
triage-needed
microsoft/vscode-python-debugger#1104 · 1 reacción · 1 asignado ·
-
triage-needed
Dificultad 4/5 3-5 días Aptitud para principiantes 58/100
microsoft/vscode-python-debugger#1095 · 1 comentario · 1 reacción ·
Todos los issues de microsoft/vscode-python-debugger
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
security
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
IBM/node-sdk-core#373 ·
-
e2e-failure ready-to-code
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100