("command liveshare.join not found")

[toralf]

Describe what happened:

What was your system configuration? Product and Version [VS/VSCode]: 1.68 OS Version[macOS/Windows]: Gentoo Linux Live Share Extension Version:v1.0.5615 Target Platform or Language [e.g. Node.js]:16.15.1

Steps to Reproduce / Scenario: Try to join a session

I updated icu at my stable hardened Gentoo 2 days ago from dev-libs/icu-70.1-r1 to dev-libs/icu-71.1-r1 and are faced now with a borken liveshare ("command liveshare.join not found"). Toggeling the developer tools reveals:

Activating extension 'ms-vsliveshare.vsliveshare' failed: Agent terminated with exit code: 0 and signal null: Process terminated. Couldn't find a valid ICU package installed on the system. Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.
   at System.Environment.FailFast(System.String)at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode()
   at System.Globalization.GlobalizationMode..cctor()
   at System.Globalization.CultureData.CreateCultureWithInvariantData()
   at System.Globalization.CultureData.get_Invariant()
   at System.Globalization.CultureInfo..cctor()
   at System.String.ToLowerInvariant()
   at System.Text.EncodingHelper.GetCharset()
   at System.Text.EncodingHelper.GetEncodingFromCharset()
   at System.ConsolePal.GetConsoleEncoding()
   at System.Console+<>c.<get_OutputEncoding>b__19_0()
   at System.Threading.LazyInitializer.EnsureInitializedCore[[System.__Canon, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](System.__Canon ByRef, System.Object ByRef, System.Func`1<System.__Canon>)
   at System.Threading.LazyInitializer.EnsureInitialized[[System.__Canon, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](System.__Canon ByRef, System.Object ByRef, System.Func`1<System.__Canon>)
   at System.Console.get_OutputEncoding()
   at System.Console.CreateOutputWriter(System.IO.Stream)
   at System.Console+<>c.<get_Out>b__26_0()
   at System.Threading.LazyInitializer.EnsureInitializedCore[[System.__Canon, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](System.__Canon ByRef, System.Object ByRef, System.Func`1<System.__Canon>)
   at System.Threading.LazyInitializer.EnsureInitialized[[System.__Canon, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](System.__Canon ByRef, System.Object ByRef, System.Func`1<System.__Canon>)
   at System.Console.get_Out()
   at Microsoft.Extensions.CommandLineUtils.CommandLineApplication..ctor(Boolean)
   at Microsoft.Cascade.Agent.Program..ctor()
   at Microsoft.Cascade.Agent.Program.Main(System.String[]).
$onExtensionActivationError	@	mainThreadExtensionService.ts:111

Going back here isn't possible due to the big dep graph, resulting in 24 hours compile time. Any hints how to circumvent his issue are welcome.

[Ten0]

Same issue on up-to-date Arch s. I'm not sure what

Set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support.
   at System.Environment.FailFast(System.String)at System.Globalization.GlobalizationMode.GetGlobalizationInvariantMode()

means but if somebody knows I'd be willing to try this. (What is globalization support?)

[Ten0]

Ok looks like launching vscode with:

DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 code

is a workaround

[mikefossa]

Ok looks like launching vscode with:

DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 code

is a workaround

This fixed it for me on Arch Linux using visual-studio-code-bin 1.69.2-1

[toralf]

Ok looks like launching vscode with:

DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1 code

is a workaround

yep, used it here too for a while now.

[derekbekoe]

We’ve made improvements in this area since this issue was filed (i.e. the vsls-agent process and associated .NET/Linux dependencies have been removed). We believe this may have improved your experience and are closing this issue. If this issue still persists for you, please comment on the issue and let us know. Thank you.