Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.100.3
- OS Version: Darwin arm64 24.5.0
Steps to Reproduce:
- Switch the UI language to non-English, e.g. Chinese
- Connect to a remote server.
- Notice almost all UI elements are translated, except for those contributed by built-in extensions, e.g. The source control view.
vscode-remote-i18n-issue.mp4
(This reproduction video is captured by @BlackHole1.)
We have submitted a fix #249430.
Activity
lszomoru commentedon Jun 4, 2025
@TylerLeonhardt, could you please take a look at this! Thanks!
3 remaining items
alexr00 commentedon Jul 2, 2025
Looks like this is still happening:
hyrious commentedon Jul 3, 2025
@alexr00 Try restart the code server because the
clp
folder must (will explain below) be generated on the second start of a fresh install.The
clp
generation needs bothnls.*.json
(in theout
folder) andlanguagepacks.json
(in the userdata
folder) having correct content BEFOREserver-main.js
starting. We can see thatlanguagepacks.json
is only generated when you're switching languages from the front-end.So here's the detailed steps to enable language packs in remote server:
~/.vscode-server-insiders/data/languagepacks.json
depending on your remote type.killall code-server-insiders node
. Then you can simply do reload window.clp
folder should be generated. For correctness you can check for paths like~/.vscode-server-insiders/data/clp/{hash}.{lang}/
depending on your remote type.BlackHole1 commentedon Jul 3, 2025
Area.mp4
alexr00 commentedon Jul 3, 2025
This does work after restarting the remote server. @TylerLeonhardt in case you want to consider this verified.
TylerLeonhardt commentedon Jul 9, 2025
No I think we should handle this better. We should show a notification when we were unable to fetch the translations and offer a restart to apply the extension that was just installed.
It was suppose to work this way even before the most recent PR, but perhaps something else broke along the way
hyrious commentedon Jul 9, 2025
In case it helps, the remote code server's setup & start is managed by the remote extensions (Remote SSH, Dev Containers, etc). Remote SSH does provide a command
Kill VS Code Server on Host
while Dev Containers do not have a way to kill the server.