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

Hot exit: folders with backups no longer restore #90949

Closed
bpasero opened this issue Feb 19, 2020 · 4 comments
Closed

Hot exit: folders with backups no longer restore #90949

bpasero opened this issue Feb 19, 2020 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority verified Verification succeeded workbench-hot-exit Preservation of unsaved changes across restarts
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Feb 19, 2020

Steps to Reproduce:

  1. open a folder
  2. make some files dirty
  3. close the window
  4. from the command line open code with a different folder

=> 🐛 the folder opens but I would expect a second window opening with the dirty files from the first session

I think this somewhat broke with 7b681aa where I see that we now seem to be adding these folders (looking for backupMainService.getFolderBackupPaths()).

The idea behind hot exit was always that a user would get all sessions with dirty files back as a window when started on a different workspace (@Tyriar correct me if we changed that assumption).

@bpasero bpasero added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority workbench-hot-exit Preservation of unsaved changes across restarts labels Feb 19, 2020
@bpasero
Copy link
Member Author

bpasero commented Feb 19, 2020

Was this supposed to be:

foldersToOpen.push(...foldersToRestore.map(f => ({ folderUri: f, remoteAuhority: getRemoteAuthority(f), isRestored: true })));

?

@aeschli
Copy link
Contributor

aeschli commented Feb 19, 2020

Yes, you are correct!

@aeschli aeschli added this to the February 2020 milestone Feb 19, 2020
@Tyriar
Copy link
Member

Tyriar commented Feb 19, 2020

The idea behind hot exit was always that a user would get all sessions with dirty files back as a window when started on a different workspace

Yes, by default all backed up workspaces would restore whenever VS Code is launched

image

@bpasero
Copy link
Member Author

bpasero commented Feb 19, 2020

This will probably come to a surprise for many people once they update to next stable where we would restore all workspaces with untitled files at once. I find it interesting that no one complained so far, this might backfire :)

@bpasero bpasero added the verified Verification succeeded label Feb 25, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Apr 4, 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 important Issue identified as high-priority verified Verification succeeded workbench-hot-exit Preservation of unsaved changes across restarts
Projects
None yet
Development

No branches or pull requests

3 participants