Unable to install extension 'ms-vscode-remote.remote-wsl' as it is not compatible with VS Code '1.63.2'.

[eabase]

Describe the bug

Following these instructions, I am trying to install the Remote WSL extension:

• https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl

Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

IDK, I don't intend to use VSCode.

Please confirm that the issue/resolution isn't already documented

• I checked the Docs page and my issue is not mentioned there.

Instructions are not clear and json already has the extension there.

• https://github.com/VSCodium/vscodium/blob/master/DOCS.md#proprietary-extensions

To Reproduce
Steps to reproduce the behavior:

Normal extension installation

Expected behavior

It would work

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Mac OS, Ubuntu 20.04, etc]
• Architecture [e.g. x64, ia32, arm64]
• Version [e.g. 1.33.0]

Additional context
Add any other context about the problem here.

[daiyam]

Incompatibility due to licensing

[eabase]

@daiyam
Well, that is just ...eh hum.. 👎 , because I have already accepted all other licenses including VSCode on other machines I'm accessing. In addition all the remote extensions are already present in the VSCodium product.json so obviously there must be a way to make this work, as indicated by the DOCS.md, just that it doesn't make sense as written. (Perhaps on purpose?)

---

I managed to manually install the extension simply by matching the version in the package.json, but then it would fail (as reported everywhere) with:

/c/Users/xxxx/.vscode-oss/extensions/ms-vscode-remote.remote-wsl-0.64.2/scripts/wslServer.sh: 50: /c/Users/xxxx/.vscode-oss/extensions/ms-vscode-remote.remote-wsl-0.64.2/scripts/wslServer.sh: /home/zzzz/.vscode-server-oss/bin/899d46d82c4c95423fb7e10e68eba52050e30ba3/bin/undefined: not found

This is because they messed up the code, wslCode.sh and wslServer.sh scripts.

The last line in wslCode.sh should not have the remote-cli, it seem:

# Nice function to dump out a lot of info that is hard to see.
# I put this in all scripts... 
show_it () {
	hline="-----------------------------------------------------------------------"
	echo -e "\n\n"
	echo "${hline}"
	echo "  This Script variables:"
	echo "${hline}"
	
	# The actual variables
	echo "  \$0 <this path>       : $0"

	echo "  VSCODE_WSL_DEBUG_INFO : ${VSCODE_WSL_DEBUG_INFO}"
	echo "  WSL_DISTRO_NAME       : ${WSL_DISTRO_NAME}"
	echo "  COMMIT                : ${COMMIT}"
	echo "  APP_NAME              : ${APP_NAME}"
	echo "  QUALITY               : ${QUALITY}"
	echo "  NAME                  : ${NAME}"
	echo "  SERVERDATAFOLDER      : ${SERVERDATAFOLDER}"
	echo "  DATAFOLDER            : ${DATAFOLDER}"
	echo "  VSCODE_PATH           : ${VSCODE_PATH}"
	echo "  ELECTRON              : ${ELECTRON}"

	echo "${hline}"	
	echo -e "  [options] :\n${@}\n"

	echo "${hline}"	
	echo "  IN_WSL                : ${IN_WSL}"
	echo "  WSLPATH               : ${WSLPATH}"
	echo "  WSLENV                : ${WSLENV}"
	echo "  WSL_BUILD             : ${WSL_BUILD}"
	echo "  WSL_EXT_WLOC          : ${WSL_EXT_WLOC}"
	echo "  WSL_CODE              : ${WSL_CODE}"
	echo "  VSCODE_REMOTE_BIN     : ${VSCODE_REMOTE_BIN}"
	echo "  AUTHORITY             : ${AUTHORITY}"

	echo "${hline}"	
	echo "  PIPE_INPUT_FILE             : ${PIPE_INPUT_FILE}"
	echo "  VSCODE_CLIENT_COMMAND       : ${VSCODE_CLIENT_COMMAND}"
	echo "  VSCODE_CLIENT_COMMAND_CWD   : ${VSCODE_CLIENT_COMMAND_CWD}"
	echo "  VSCODE_CLI_AUTHORITY        : ${VSCODE_CLI_AUTHORITY}"
	echo "  VSCODE_CLI_REMOTE_ENV       : ${VSCODE_CLI_REMOTE_ENV}"
	echo "  VSCODE_STDIN_FILE_PATH      : ${VSCODE_STDIN_FILE_PATH}"
	echo "  WSLENV                      : ${WSLENV}"

	echo "${hline}"	
}

show_it


#...

echo "  Running:  VSCODE_REMOTE_BIN ..."

VSCODE_CLIENT_COMMAND="$WIN_CODE_CMD" \
VSCODE_CLIENT_COMMAND_CWD="$(dirname "$0")" \
VSCODE_CLI_AUTHORITY="$AUTHORITY" \
VSCODE_CLI_REMOTE_ENV="$STORED_ENV" \
VSCODE_STDIN_FILE_PATH="$PIPE_INPUT_FILE" \
WSLENV="VSCODE_CLI_REMOTE_ENV/w:$WSLENV" \
show_it && "$VSCODE_REMOTE_BIN/$COMMIT/bin/$APP_NAME" "$@"
#show_it && "$VSCODE_REMOTE_BIN/$COMMIT/bin/remote-cli/$APP_NAME" "$@"

Then I also soft-linked the code to codium

This finally generate the "error":

# C:\path_to_\github_clone\vscode\src/vs/server/node/server.cli.ts
console.log('Command is only available in WSL or inside a Visual Studio Code terminal.')

Anyway, I am not going to spend more time trying to make this blatant anti-OSS work. Clearly looking in the obfuscated JS sources for the ms-vscode-remote.remote-wsl we find how an incredible amount of time and effort is spent sending your personal usage data into the cloud. Seemingly the telemetry code base is many times that of the extension itself! So whatever your opinion is about this, we'we already paid too much for that crap license.

[daiyam]

Yep! An OSS alternative would the best solution since it could be shared.