fix(debugger): debug uv / poetry run configurations in the project's environment

A Python run configuration such as `uv run python main.py` or `poetry run pytest` was debugged as `python3 -m uv run python main.py`: debugpy treated the manager as a console script and ran it as a module, so the session failed or ran outside the project's environment. Configurations that run through uv, poetry, pdm, pipenv, hatch or rye now pass the manager to debugpy as the debuggee's interpreter (`["uv", "run", "python"]`) and keep the script, `-m` module or tool (`uv run pytest` → module `pytest`) as the target. The adapter and its launcher run on a plain interpreter (`debugLauncherPython`), which the backend now prefers when choosing the adapter's command.
2026-11-08 08:08:16 -10:00 · 2026-11-05 08:17:55 +08:00
1 changed files with 2 additions and 6 deletions
@@ -62,9 +62,9 @@
 .icon {
  flex: none;
 }
-/* The name takes the whole row; when it doesn't fit, the grey detail after it gives way first. */
 .label {
-  flex: 0 1 auto;
+  flex: 0 0 auto;
+  max-width: 75%;
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
@@ -74,7 +74,6 @@
  font-weight: 600;
 }
 .detail {
-  flex: 0 10000 auto;
  min-width: 0;
  overflow: hidden;
  text-overflow: ellipsis;
@@ -191,9 +190,6 @@
  align-items: center;
  gap: 8px;
 }
-.stashRow > .detail {
-  flex-shrink: 1;
-}
 .stashMessage {
  flex: 1;
  min-width: 0;