-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Server crashing with CultureNotFoundException (en-us is an invalid culture identifier) #386
Comments
cc @jbevain In this case, it is not related to our Unity extension. The .NET server part is crashing getting @devrandomzero could you share your locale settings in VSCode, but also for your system-OS (like what are the regions/languages supported). Thank you! It seems the associated runtime is running in |
Thank you @sailro, here's my system locale:
Hope is enough |
I have the same issue except I am not using Unity. I am using Remote-SSH to a RHEL 7.9 machine. When the C# DevKit extension activates, I get the exact same error. We are using Invariant mode for globalization, i.e. DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=1. |
Yes I think that is the root issue, the C# Dev Kit server-part should handle that the associated runtime is setup for invariant culture, providing at least a fallback to a default culture when hitting such a It seems there is not current API for detecting this invariant mode: But an API proposal was submitted: cc @AArnott for awareness. |
What is the purpose for setting |
From what I understand, specific Linux distributions are made to be super small like That's why this flag was introduced to allow the .NET runtime to work on those systems knowing the drawback will be poor globalization support. Microsoft is even offering Docker files for So clearing @devrandomzero @sean-jost do you have a similar use case ? |
Thanks. The next prerelease will swallow this exception. |
@sailro It is very strange because when I query locale settings via |
@sailro I've also tried to set in my env DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=0 but the problem persists. |
... or maybe next week's. We're having some trouble with some other changes and they may cause this fix to not quite make this week's release. |
Hi, any news about this? Thank you |
It should be released, make sure you are using pre-releases (go to Extensions, C# Dev Kit and click Switch to Pre-Release version) |
Hi,
Then sometimes when I try to use the autocomplete function I get this error and a popup in the bottom right corner with this message
VS Code = v1.82.2-1 Thank you for your help |
Indeed, it seems it was correctly fixed in C# Dev Kit by @AArnott (we just have a warning to track that a specific culture was not found). But this line is wrong in Roslyn in the context of cc @CyrusNajmabadi and @genlu, for more context see #386 (comment) cc @jbevain |
What is the right way to get the english culture (or some reasonable fallback culture) in that case? |
@CyrusNajmabadi I think all you have is |
@CyrusNajmabadi check this comment #386 (comment) |
Ok. Opened dotnet/roslyn#70096 as the poor-man's way of handling this. |
Type: Bug
I'm using the new Unity extension with C# Dev Kit and as the title says the autocompletion doesn't work, I've tried to follow all the steps mentioned in this post and I think the problem is here:
3- Make sure C# Dev Kit is not displaying any error message
Here's the extension output:
Thanks
Extension version: 0.4.2
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:18:39.991Z)
OS version: Linux x64 6.4.9-arch1-1
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: disabled_software
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: