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

Test: Improvements to Edit Sessions debug view #161860

Closed
3 tasks done
joyceerhl opened this issue Sep 26, 2022 · 2 comments
Closed
3 tasks done

Test: Improvements to Edit Sessions debug view #161860

joyceerhl opened this issue Sep 26, 2022 · 2 comments

Comments

@joyceerhl
Copy link
Contributor

joyceerhl commented Sep 26, 2022

Refs #156334, #156337

Authors: @joyceerhl

Complexity: 2

Create Issue


We have an Edit Sessions view for debugging purposes. This view now shows you which machine each Edit Session originates from.

  1. Have some uncommitted edits in a desktop git clone of a repo or a vscode.dev repo
  2. Run Store Current Edit Session (ideally, do this from a couple of different places, e.g. VS Code desktop as well as VS Code for the web)
  3. Run Show Edit Sessions
  4. Verify that the Edit Sessions view now tells you which machine each Edit Session came from
  5. Verify that the tree node is now the repo name instead of a GUID
@sandy081
Copy link
Member

There was one moment where it worked flawlessly that I could see sessions in browser and desktop and delete them. But most of the times I hit issues with long loading requests.

@gregvanl
Copy link

Part of the trouble I've been having may be that I don't understand how Edit Sessions are meant to work. My mental model was they were snapshots that could be applied manually to move a repo to a specific state.
It appears that Edit Sessions are more of an automatic way to apply changes to a repo when you reopen a VS Code instance on a repo which has a store Edit Session. I found the feature pretty confusing

@gregvanl gregvanl removed their assignment Sep 28, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants