-
Notifications
You must be signed in to change notification settings - Fork 30k
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
LiveShare: error on guest about files.hotExit not applicable as workspace setting #89404
Comments
|
Since I tried to reproduce with stable where it does not reproduce, I do not think it is their code to blame (unless they install a different version to insiders compared to stable?). Maybe @IlyaBiryukov can chime in |
Let me also check from the extension's code perspective if there is any change. |
It looks like error is always thrown but not surfaced in UI. Change is that the error is now surfaced in UI which should not be. |
Live Share sets 'files.hotExit' as a workspace setting. It has been doing this for quite some time. I guess we need to remove it because, as you said, it doesn't work on a workspace level. |
@IlyaBiryukov I guess this was done partially due to issues outlined in #53257. At least for readonly sessions, this should no longer be an issue anymore given readonly files no longer mark as dirty in the guest. |
Steps to Reproduce:
=> 🐛 notice this error right on startup
I cannot reproduce in Code stable, so I suspect a regression with our configuration API.
The text was updated successfully, but these errors were encountered: