vscode: CLI prints wrong version after extension has been successfully installed
Does this issue occur when all extensions are disabled?: Yes/No
đ Not relevant.
- VS Code Version: 1.65.2, c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, x64
- OS Version: Debian 11 (bullseye)
Steps to Reproduce:
- On a Machine (arch:
x86_64
) running docker:
docker run --rm -ti debian:bullseye
- Within the container:
apt update \
&& apt install -y --no-install-recommends \
ca-certificates \
gnupg \
libasound2 \
libgbm1 \
libgtk-3-0 \
libnss3 \
libsecret-1-0 \
libxkbfile1 \
libxshmfence1 \
libxss1 \
wget \
&& wget https://update.code.visualstudio.com/1.65.2/linux-deb-x64/stable \
-O code_1.65.2-1646927742_amd64.deb \
&& dpkg -i code_1.65.2-1646927742_amd64.deb
useradd -ms /bin/bash coder \
&& su - coder
Executing
code --install-extension ms-toolsai.jupyter
results in
Installing extensions...
Installing extension 'ms-toolsai.jupyter'...
(node:4414) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `code --trace-deprecation ...` to show where the warning was created)
Extension 'ms-toolsai.jupyter' v2022.5.1001601848 was successfully installed.
đ v2022.5.1001601848 of ms-toolsai.jupyter is not compatible with Code 1.65.2.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 28 (9 by maintainers)
Retested with
1.70.0
as1.71.0
is out now:x86_64
) running docker:Executing
results in
â Correct version of installed extension is printed. Fixed since code
1.70.0
. âšī¸v2022.8.1002431955
of ms-toolsai.jupyter is currently the latest [stable] version.Ok, I think its a printing issue in the CLI. Even though it says
Extension 'ms-toolsai.jupyter' v2022.6.1201981810 was successfully installed.
when you check in the UIv2022.5.1001601848
is installed. Can you please confirm?Will fix the printing.
@TylerLeonhardt I will test it with the next version as soon as the version after next is released.
If the issue is not resolved, I will reopen it.
@benz0li I am really sorry that I am not able to understand the issue now. VS Code (CLI / UI) always installs the latest compatible version of the extension. They shall behave similarly. From your videos and comments, I infer that both are doing the same. If not, can you please explain the different behaviour you are seeing?
If it is fixed in latest version, we would recommend to use the latest. So can you please check with the latest version of VS Code?