| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Exposes debugpy's breakOnSystemExit option (microsoft/debugpy#2017) in the extension's launch.json/attach configuration schema and TypeScript debug config types. Accepts an array of exit codes and/or inclusive {from,to} ranges to control which SystemExit codes cause the debugger to break. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 24c2d34b-15f0-45d2-bd59-8ee042269d20
Describe the default as an ignore-list ({0, None}, plus 3 under Django/Flask) that breaks on any other code when uncaught-exception breaking is enabled, rather than the looser 'break on all non-zero exit codes'.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 24c2d34b-15f0-45d2-bd59-8ee042269d20
| Back | FazBrowse Home | New Git URL |
Exposes debugpy's new breakOnSystemExit option (microsoft/debugpy#2017) in the extension's launch.json / attach configuration schema, as requested in microsoft/debugpy#1591.
What
Behavior
breakOnSystemExit accepts an array of exit codes and/or inclusive { "from", "to" } ranges, controlling which SystemExit codes cause the debugger to break:
The value is passed straight through to debugpy, which parses it; no config-resolver changes are required.
Testing