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

Today's VS Code Insiders server fails on Darwin #145413

Closed
connor4312 opened this issue Mar 18, 2022 · 3 comments · Fixed by #145509
Closed

Today's VS Code Insiders server fails on Darwin #145413

connor4312 opened this issue Mar 18, 2022 · 3 comments · Fixed by #145509
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders macos Issues with VS Code on MAC/OS X verified Verification succeeded
Milestone

Comments

@connor4312
Copy link
Member

connor4312 commented Mar 18, 2022

I noticed in the launcher that today's Darwin server has a nested subdirectory, vscode-server-darwin. This broke our launcher (I initially assumed we changed something), and after checking I noticed that it also causes remote ssh to fail since the binaries are no longer in the expected locations:

local-server-1> ssh child died, shutting down

[10:38:15.018] Failed to parse remote port from server output
[10:38:15.019] Resolver error: Error: 
	at Function.Create (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:586041)
	at Object.t.handleInstallOutput (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:584693)
	at Object.e [as tryInstallWithLocalServer] (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:625033)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async /Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:644070
	at async Object.t.withShowDetailsEvent (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:647817)
	at async /Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:623505
	at async b (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:620011)
	at async Object.t.resolveWithLocalServer (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:623120)
	at async Object.t.resolve (/Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:645427)
	at async /Users/connor/.vscode-insiders/extensions/ms-vscode-remote.remote-ssh-0.77.2022031115/out/extension.js:1:722867

On the launcher side I can verify that pulling in yesterday's version by adding ?vscode-version=db0525ff4ba814780e901a5b9e399aaf596b9b20 to the vscode.dev URL fixes the issue

@connor4312 connor4312 added important Issue identified as high-priority and removed important Issue identified as high-priority labels Mar 18, 2022
@connor4312
Copy link
Member Author

connor4312 commented Mar 18, 2022

The SSH issue was a separate local problem. Looking at the directories, the contents seem mostly the same structure wise. Not sure why it's extracting differently, since it does not seem to affect remote SSH. Looking into it.

@connor4312
Copy link
Member Author

connor4312 commented Mar 18, 2022

Okay, that was a fun investigation. Yesterday's server's download path was

https://az764295.vo.msecnd.net/insider/db0525ff4ba814780e901a5b9e399aaf596b9b20/vscode-server-darwin.zip

But today's was

https://az764295.vo.msecnd.net/insider/d572d6e9d1282b352227916cb8f95bb2b03ddcaa/vscode-server-darwin-x64.zip

We would only pop off the first segment of the path when unzipping if it matched the zip name. While the zip was renamed, its nested vscode-server-darwin directory was not, and therefore we would end up with an extra segment in the path. I'll change our logic to just always pop off the first segment, though I think having the zip name match any nested directory is pretty standard so I'll leave this open in case this is worth a tweak.

@tanhakabir
Copy link
Contributor

Related to #145226 and microsoft/vscode-remote-release#4069

@connor4312 connor4312 assigned deepak1556 and unassigned weinand Mar 18, 2022
@deepak1556 deepak1556 added bug Issue identified by VS Code Team member as probable bug macos Issues with VS Code on MAC/OS X engineering VS Code - Build / issue tracking / etc. labels Mar 20, 2022
@deepak1556 deepak1556 added this to the March 2022 milestone Mar 20, 2022
@roblourens roblourens added the verified Verification succeeded label Mar 25, 2022
@github-actions github-actions bot locked and limited conversation to collaborators May 5, 2022
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 engineering VS Code - Build / issue tracking / etc. insiders-released Patch has been released in VS Code Insiders macos Issues with VS Code on MAC/OS X verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@roblourens @deepak1556 @weinand @connor4312 @tanhakabir and others