Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[debug] cancellation of attach by PID leaves dangling promises #7316

Open
AlexTugarev opened this issue Mar 11, 2020 · 3 comments
Open

[debug] cancellation of attach by PID leaves dangling promises #7316

AlexTugarev opened this issue Mar 11, 2020 · 3 comments
Assignees
Labels
bug bugs found in the application debug issues that related to debug functionality vscode issues related to VSCode compatibility

Comments

@AlexTugarev
Copy link
Contributor

While testing #7314 I learned about a dangling promise, which causing a never ending progress. When you try to attach to a running process, but then dismiss the quick open menu with esc, the awaiter will never continue at

await this.fireWillStartDebugSession();

2020-03-11 11 41 02

cc. @akosyakov

@akosyakov akosyakov self-assigned this Mar 11, 2020
@akosyakov akosyakov added bug bugs found in the application debug issues that related to debug functionality progress issues related to the progress functionality labels Mar 11, 2020
@akosyakov
Copy link
Member

I think it is caused by #5764 and #5764.

The fix is here in gitlens PR: 9c7d064

I will extract it to a separate PR then.

@akosyakov akosyakov removed their assignment Mar 12, 2020
@akosyakov
Copy link
Member

akosyakov commented Mar 12, 2020

No, it is something else. It looks like debugger can participate in the variable resolution: https://github.com/microsoft/vscode-node-debug/blob/501ceedca3b4e8aa1d0f62780558a0102dc8930a/package.json#L163-L165

So for us variable PickProcess never resolves to extension.pickNodeProcess

Edit: nope it does not seem to be a reason as well, although we are missing it.

@akosyakov akosyakov added vscode issues related to VSCode compatibility and removed progress issues related to the progress functionality labels Mar 12, 2020
@akosyakov
Copy link
Member

So it is combination of #7316 (comment) and #7316 (comment) what causing it.

@akosyakov akosyakov self-assigned this Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bugs found in the application debug issues that related to debug functionality vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

2 participants