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

LiveShare: error on guest about files.hotExit not applicable as workspace setting #89404

Closed
bpasero opened this issue Jan 28, 2020 · 6 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues regression Something that used to work is now broken verified Verification succeeded
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Jan 28, 2020

Steps to Reproduce:

  1. use insiders
  2. install LiveShare
  3. host a session
  4. join from another insiders run (via user-data-dir trick)

=> 🐛 notice this error right on startup

Screenshot 2020-01-28 at 09 18 28

I cannot reproduce in Code stable, so I suspect a regression with our configuration API.

@bpasero bpasero added config VS Code configuration, set up issues regression Something that used to work is now broken labels Jan 28, 2020
@sandy081 sandy081 modified the milestones: February 2020, January 2020 Jan 28, 2020
@sandy081 sandy081 added the bug Issue identified by VS Code Team member as probable bug label Jan 28, 2020
@sandy081
Copy link
Member

files.hotExit is an application setting and we never supported writing an application setting into workspace. Please check if something has changed with the live share extension.

@sandy081 sandy081 added info-needed Issue requires more information from poster and removed bug Issue identified by VS Code Team member as probable bug regression Something that used to work is now broken labels Jan 28, 2020
@sandy081 sandy081 removed this from the January 2020 milestone Jan 28, 2020
@bpasero
Copy link
Member Author

bpasero commented Jan 28, 2020

@sandy081

Please check if something has changed with the live share extension

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

@sandy081
Copy link
Member

Let me also check from the extension's code perspective if there is any change.

@sandy081
Copy link
Member

sandy081 commented Jan 28, 2020

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.

@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug regression Something that used to work is now broken and removed info-needed Issue requires more information from poster labels Jan 28, 2020
@sandy081 sandy081 added this to the January 2020 milestone Jan 28, 2020
@IlyaBiryukov
Copy link

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.

@bpasero
Copy link
Member Author

bpasero commented Jan 29, 2020

@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.

@connor4312 connor4312 added the verified Verification succeeded label Jan 31, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug config VS Code configuration, set up issues regression Something that used to work is now broken verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants