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

Continue on does not provide a way to move to a different machine. #162276

Open
karthiknadig opened this issue Sep 28, 2022 · 5 comments
Open

Continue on does not provide a way to move to a different machine. #162276

karthiknadig opened this issue Sep 28, 2022 · 5 comments
Assignees
Labels
continue-working-on feature-request Request for new features or functionality
Milestone

Comments

@karthiknadig
Copy link
Member

Testing #161875

There is no way to save session to move to different machine, when using the continue on command.

@joyceerhl joyceerhl added the feature-request Request for new features or functionality label Sep 28, 2022
@joyceerhl joyceerhl modified the milestones: October 2022, Backlog Sep 28, 2022
@karthiknadig
Copy link
Member Author

Edit Session: Save current session did not work for me.

@joyceerhl
Copy link
Collaborator

@karthiknadig what did you see when you ran the store current session command? Do you have the Log (Edit Sessions) output channel contents by any chance?

@karthiknadig
Copy link
Member Author

karthiknadig commented Sep 28, 2022

I closed the original session, but when i try again this is what I see:

vscode.dev (accessed from laptop1)

[2022-09-28 16:04:01.746] [editsessions] [info] Storing edit session...
[2022-09-28 16:04:02.020] [editsessions] [info] Stored edit session with ref 68194abb-97da-4b5e-b4ef-b1640c253d24.

Desktop insiders (linux on laptop 2):

[2022-09-28 16:05:39.019] [editsessions] [info] Resuming edit session, reason: edit sessions enabled...
[2022-09-28 16:05:39.019] [editsessions] [info] Resuming edit session...
[2022-09-28 16:05:40.607] [editsessions] [info] Searching for existing authentication session with ID 843eaf3d-535f-48b6-b424-e17a95dd4184
[2022-09-28 16:05:43.943] [editsessions] [info] Found existing authentication session with ID 843eaf3d-535f-48b6-b424-e17a95dd4184
[2022-09-28 16:05:44.467] [editsessions] [info] Matching identity {"remote":"[email protected]:karthiknadig/vscode-python.git","ref":"fix_activation","sha":"2eb34e57020fd6e5c4389a5e4047927a30c4a333"} against edit session folder identity {"remote":"https://github.com/karthiknadig/vscode-python","ref":"fix_activation","sha":"983ae1527e5d412ca74220864a7c796242ebdc0d"}...
[2022-09-28 16:05:44.468] [editsessions] [info] Skipping applying 1 changes from edit session with ref 68194abb-97da-4b5e-b4ef-b1640c253d24 as no matching workspace folder was found.
[2022-09-28 16:05:44.469] [editsessions] [info] Deleting edit session with ref 68194abb-97da-4b5e-b4ef-b1640c253d24 after successfully applying it to current workspace...
[2022-09-28 16:05:44.553] [editsessions] [info] Deleted edit session with ref 68194abb-97da-4b5e-b4ef-b1640c253d24.

@karthiknadig
Copy link
Member Author

It seems to say no match, but it was the exact same branch.

@joyceerhl
Copy link
Collaborator

joyceerhl commented Sep 29, 2022

Looks like your git remote in the destination was configured with an SSH URL but in the source it was configured with a HTTPS URL. Also, you're on the same branch but the HEAD SHA has changed. The edit session identity providers should be able to tolerate this sort of variance (even if it means we have decreased confidence that applying the edit session in this scenario will not cause conflicts).

Tracking this issue in #162120

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
continue-working-on feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants