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
Build does not wait for files to save #139764
Comments
Well I think "build/debug" is waiting for files to save, but since the save fails (requiring admin password) it ignores that and continues to run. Maybe the user needs to be asked in this case. |
Sorry I don't understand. The OP says that build/run happened before saving? Does this resolve before the escalation process is done?
|
The launcher should check the return value.
|
I see that but I would expect that it doesn't resolve while the user is typing the password and then resolves true when the password is correct. |
Oh, I suppose it bails when it shows the notification to escalate |
Whether the implementation of this API makes sense is secondary to the fact that the client ignores the contract. |
Looks like a save error is swallowed from here:
and vscode/src/vs/workbench/services/textfile/common/textFileEditorModel.ts Lines 864 to 866 in c8e2fd7
Will see if I can return |
A function that does not return anything returns |
With 42a43eb, a call to |
I think the original request is that we would wait and start debugging after "Retry as Sudo" is clicked. We don't have a way to wait on this and I wouldn't want to block debugging on a non-modal dialog anyway, so does it make sense to show a message like "Save failed, start debugging anyway?" which would show up at the same time as the "Failed to save" notification. |
Fair, but since this is not a modal dialog but just a notification the save operation at that point has just failed and the editor remains dirty until the user tries again. There is no way currently to join that via any API. |
Please read the description once more. There is no need to try again. |
Issue Type: Bug
In order to be able to run my code, I have to modify
file:///proc/sys/fs/inotify/max_user_instances first. So I did and I told VS Code to run.
This file, however, requires privilege escalation to be saved. Here is the order of events:
Here is the expected order of events:
VS Code version: Code 1.63.2 (899d46d, 2021-12-15T09:39:46.686Z)
OS version: Linux x64 5.15.8-1-default
Restricted Mode: No
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (26)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: