Allow Overwrite of Stacktrace with SupportsDelayedStackTraceLoading
@connor4312 y travaille déjà.
Depuis le 12/10/2024.
Évaluation
Cette issue n'a pas encore été évaluée.
Description
I have a situation where calculating my stacktrace is expensive (takes 300ms-800ms in PowerShell for "reasons").
Editors such as vscode will not display where they are stopped until they receive the first stackTrace frame, then they will background the remainder stacktrace fetch if SupportsDelayedStackTraceLoading is specified. Because of this, stepping in the PowerShell debug adapter feels "slow" as the editor will not respond until I can give it at least one stack trace.
I can send it a "dummy" breakpoint frame immediately that is 90% there with id: 0 in order to get the editor UI to respond quickly, but if the editor requests the next stackTrace by startFrame at 1, if I "spuriously" supply it again via id:0 it still gets appended to the call stack list rather than replace what is in the call stack.
Before I can ask in vscode to change this behavior, it should be less ambiguous in the spec, so either a statement that says subsequent stacktrace requests with the same ID should overwrite the existing stacktraces if spuriously received outside the requested range, or allow an additional method before stacktrace (or additional property as part of stopped event) that allows specifying the breakpoint location so the editor can immediately place its pointer there while backgrounding for further callstack/stacktrace info.
Thanks!
- Langage dominant
- HTML
- Étoiles
- 1.8k
- Forks
- 173
- Merge moyen
- 7 j 7 h
- PR mergées (30 j)
- 2
Préparer son environnement
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoft/debug-adapter-protocol
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 35/100
microsoft/debug-adapter-protocol#633 · 1 commentaire ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 42/100
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 35/100
microsoft/debug-adapter-protocol#599 · 8 réactions ·
-
under-discussion
Difficulté 2/5 1-3 heures Accessibilité débutants 48/100
microsoft/debug-adapter-protocol#596 · 9 commentaires ·