Try run "Remote-SSH" extension in "Code - OSS" fails #162874

Does this issue occur when all extensions are disabled?: ??

Replaced by bug-on-extension

• VS Code Version: 1.71.2
• OS Version: macOS-12.6

Steps to Reproduce:

1. clone and build vscode, producing Code-OSS
2. Running vscode-oss, install extension "Remote-SSH"
3. try connect to remote host; provoking extension to install remote-server
4. connect to remote works, scp works, but
5. installing remote-server fails

[12:17:58.282] > vscode-scp-done.flag                          100%    9     1.9KB/s   00:00    
[12:17:58.543] "Copy server to host" terminal command done
[12:18:00.635] > Found flag and server on host
[12:18:00.642] > 4d1f898c4a21%%2%%
> tar --version:
[12:18:00.645] > bsdtar 3.3.2 - libarchive 3.3.2 zlib/1.2.11 liblzma/5.0.5 bz2lib/1.0.6
[12:18:02.860] stderr> mv: rename vscode-server-darwin/bin to ./bin: Directory not empty
[12:18:02.860] stderr> mv: rename vscode-server-darwin/extensions to ./extensions: Directory not empty
[12:18:02.860] stderr> mv: rename vscode-server-darwin/node_modules to ./node_modules: Directory not empty
[12:18:02.861] > ERROR: /Users/user/.vscode-server-oss/bin/6a25ae3a24929f35aabf8a051531c0716032e0a0/node or /Users/user/.vscode-server-oss/bin/6a25ae3a24929f35aabf8a051531c0716032e0a0/bin/code-server-insiders don't exist
[12:18:02.861] stderr> mv: rename vscode-server-darwin/out to ./out: Directory not empty
[12:18:02.864] > Already attempted local download, failing

Connecting/installing from 'stock' vscode works.

My goal is to test/debug to see how my fork interacts with Remote-SSH.
I notice that the extension creates a new window... is that a new instance of vscode?
Is there a way to run the stock vscode but have it create the new/ssh instance running vscode-oss ?

Or: is there a document that explains the how the SSH extension works? What the remote-server does?
[something easier that reverse-engineering from the source code...]

Or: For my current question: what is the URI that is used in the TextEditorModel ?
Is it a simple file://path/file.ext that is interpreted by the remote-server?
or is it like: ssh://host/path/file.ext.ssh ?