Support for connecting to Apple Silicon/M1/ARM64 remote

[smokris]

When I use Visual Studio Code 1.51.1 running on macOS 11.0.1 x86_64 and attempt to connect using remote-ssh 0.56.0 to a macOS 11.0.1 arm64 system, the VS Code Server fails to start on the remote system:

[13:47:19.278] > /Users/…/.vscode-server/bin/e5a624b788d92b8d34d1392e4c4d9789406efe8f/server.sh: line 12: /Users/…/.vscode-server/bin/e5a624b788d92b8d34d1392e4c4d9789406efe8f/node: Bad CPU type in executable

That binary is x86_64 only, whereas (in order for it to work natively / without needing the Rosetta translation layer) it should be arm64 or "Universal" (x86_64 + arm64).

$ file .vscode-server/bin/e5a624b788d92b8d34d1392e4c4d9789406efe8f/node
.vscode-server/bin/e5a624b788d92b8d34d1392e4c4d9789406efe8f/node: Mach-O 64-bit executable x86_64

[roblourens]

@joaomoreno are we building the server for this yet? I don't see the mac arm build on our builds page

[joaomoreno]

@deepak1556 Is the right person to ping.

[gorilla-1]

I have the same issue with my WSL at VS Code
e5a624b788d92b8d34d1392e4c4d9789406efe8f: -c: line 0: unexpected EOF while looking for matching

[deepak1556]

Yeah I had left this out for the exploration release, definitely something to add. Thanks for opening the issue!

[deepak1556]

Since we download prebuilt node binaries for the remote, and there is no arm64 version available yet. This feature cannot move forward until then.

[richiksc]

Is this feature required to move forward with microsoft/vscode#106770, and does it prevent the exploration build from being promoted to Insiders? Just curious.

[deepak1556]

Not it doesn't. Once we have vscode stable 1.52, the next insiders following it will contain mac arm builds too.