-
Notifications
You must be signed in to change notification settings - Fork 46
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
Ubuntu + Powershell 7 not finding LocalizedData #332
Comments
I'm having the same error when running I have tested with the latest 3.5.2.487 version and also the second latest 3.5.1.458 but with no luck. |
Hi @astrahan87 and @topikettunen , I'm just working on updating the CI process to simplify build and release and will try and identify the cause of this problem at the same time. @topikettunen - are you using Linux, Windows or MacOS agents? |
I use various different agents but the job where I use this module runs Linux (Ubuntu 18.04) agent. |
Thanks @topikettunen - I'm currently only testing on Ubuntu 16.04. So I'll add some tests on Ubuntu 18.04 to see if I can catch/replicate this. |
I've added the Xenial tests and will wait for them to complete: https://dscottraynsford.visualstudio.com/GitHub/_build/results?buildId=1429&view=logs&s=859b8d9a-8fd6-5a5c-6f5e-f84f1990894e It will take a while for the test runs to complete so I'll check on them tomorrow. |
@topikettunen - have replicated the issue. Looks like it only occurs on PS7 with Xenial and is to do with the case I was using to select the default culture. I've applied a fix and will aim to release tomorrow. |
Unfortunately the fix I applied didn't work. So I'm going to need to do some further investigation on this. You can see the test failure here: It appears to be an issue occurring only on Ubuntu 18.04 on PS7 when using the |
I've found the problem: The However, I can work around the issue, so I've put a fix in place and just testing now: https://dev.azure.com/dscottraynsford/GitHub/_build/results?buildId=1432&view=results |
The tests have passed, so I'll aim to release this later today. |
This has been released to the PS Gallery in 3.6.1: |
Looks like it's all working for me. Thanks! |
Issue
Details:
You've fixed the "hard" errors that were occurring with Powershell 7, but we've started seeing some non-terminating error messages related to using Powershell 7:
Just calling "Import-Module -Name CosmosDB" results in:
Seems like it's not recognizing to look in the /en-US/ subdirectory for some reason.
This was previously working with Powershell Core 6.2 (or at least erroring more quietly).
If this is a misconfiguration on our end for some reason, please let me know.
The text was updated successfully, but these errors were encountered: