Add configuration option to issue a SIGTERM when the Stop button is clicked in debugger

Offen

#316 erstellt am 15.4.2024 10 Kommentare 60 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@karthiknadig arbeitet bereits daran.

Seit 08.8.2024.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

feature-request needs community feedback

I want the ability to use the "Stop" button in the Python debugger in VS Code to send a SIGTERM (and/or maybe a SIGINT) to the running process, instead of just sending it SIGKILL (as it currently does).

This is the "Stop" button I'm talking about:

Proposed Solution

I'm thinking that a new option like this in the launch.json config file could be a good way to introduce this change without being a breaking change for the way everyone is used to the "stop" button working.

{
  "configurations": [
    {
      "name": "Python Debugger: Current File (Integrated Terminal)",
      "type": "debugpy",
      "request": "launch",
      "program": "${file}",
      "console": "integratedTerminal",
      "stop_action": "SIGKILL", // this would be a new enum-like config option, with values of "SIGKILL", "SIGINT", "SIGTERM", maybe others
    },
  ]
}

Possible additional ideas, more context

The minimum viable solution is described above.
SIGKILL (the current behavior) and SIGTERM are the two behaviors I'm personally chasing. SIGINT is another one that would be good to have as an option though.
As an extended implementation, the stop_action field could support a process like: send SIGTERM, wait 15 seconds, send SIGKILL.
This feature request stems from wanting to be able to test and debug the AWS Batch end-of-job behavior:

Under the hood, the Amazon ECS StopTask API call is used, which sends a SIGTERM value to the running container task. If after 30 seconds the container is still running, a SIGKILL signal is sent to forcibly stop the container. If the container handles the SIGTERM value gracefully and exits within 30 seconds from receiving it, no SIGKILL value is sent.

Related Previous Issues and Discussions

microsoft/vscode-python#21605
https://github.com/microsoft/debugpy/issues/500
https://github.com/microsoft/vscode-python/discussions/21582

Vorherrschende Sprache: TypeScript
Sterne: 181
Forks: 126
Ø Merge: 8 Std. 49 Min.
Gemergte PRs (30 T.): 1

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/vscode-python-debugger

Update dependencies with actionable security alerts Offen

triage-needed

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100

microsoft/vscode-python-debugger#1110 · Erstellt am 17.9.2026
PowerShell script debugpy.ps1 incorrectly handles multiple arguments passed as an array Offen

triage-needed

Schwierigkeit 1/5 1-3 Stunden Anfängerfreundlichkeit 88/100

microsoft/vscode-python-debugger#1024 · 1 Kommentar · Erstellt am 07.5.2026
Update dependencies with actionable security alerts Offen

triage-needed

microsoft/vscode-python-debugger#1111 · 1 Reaktion · 1 zugewiesene Person · Erstellt am 17.9.2026
Update vulnerable npm dependencies Offen

triage-needed

microsoft/vscode-python-debugger#1104 · 1 Reaktion · 1 zugewiesene Person · Erstellt am 14.9.2026
Attach process picker still hangs without WMIC because windows-process-tree loader misses node_modules.asar Offen

triage-needed

Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 58/100

microsoft/vscode-python-debugger#1095 · 1 Kommentar · 1 Reaktion · Erstellt am 01.9.2026

Alle Issues in microsoft/vscode-python-debugger