Interface with GSTools

Hey there,
We are working on a project for geostatistical simulaton (https://github.com/GeoStat-Framework), where we, among other things, provide tools to generate spatial random fields based on variogram methods.
Now we wanted to provide conditioned random fields by incorporating data via Kriging and stumbled over your neat project! Your input information is totally similar to our approach, so I wrote a small interface for pykrige, which looks and works like this:
import numpy as np
from gstools import Gaussian
from pykrige.ok import OrdinaryKriging

data = np.array([[0.3, 1.2, 0.47],
                 [1.9, 0.6, 0.56],
                 [1.1, 3.2, 0.74],
                 [3.3, 4.4, 1.47],
                 [4.7, 3.8, 1.74]])

gridx = np.arange(0.0, 5.5, 0.1)
gridy = np.arange(0.0, 5.5, 0.1)

# a GSTools based covariance model
model = Gaussian(dim=2, len_scale=1, anis=0.2, angles=0.5, var=0.5, nugget=0.1)

OK1 = OrdinaryKriging(
    data[:, 0], data[:, 1], data[:, 2],
    **model.pykrige_kwargs,  # magic
)
z1, ss1 = OK1.execute('grid', gridx, gridy)

We provide a flexible Covariance-Class that contains all informations about the variogram and has a huge range of methods (like spectrum, spectral density, integral scale, variogram fitting, anisotropy, rotation... and so on) You can also create user defined models by just defining a correlation function (See here: https://github.com/GeoStat-Framework/GSTools#user-defined-covariance-models)
This class now also contains a property called pykrige_kwargs which can be used with your project as shown above. Only difference:
The anisotropy ratios are calculated inversely in both packages. So anis=0.2 in GSTools will result in anisotropy_scaling=1.0/0.2 in pykrige.
The angles are also calculated differently. Your orientation is the opposite of ours and you use deg instead of rad. So angles=0.5 in GSTools will result in anisotropy_angle=-np.rad2deg(0.5) in pykrige.
Same in 3D.  pykrige_kwargs takes care of that depending on the dimension.
But still, the provided functionality overlaps perfectly! And I think, If you are still working on refactoring your code, It could be a cool thing working together!
What do you think about that? Maybe we can join forces! I'd love to have a chat about that.
Cheers,
Sebastian

We just updated our rotation behavior in GSTools (https://github.com/GeoStat-Framework/GSTools/commit/0dfaf5f2ec8563d701d4c2e6e95c60e4312c06f4), so that the orientation is the same as in PyKrige.
Also we now provide simple and ordinary kriging in GSTools and recommend your package for the more fancier stuff.
The above mentioned Interface to PyKrige will be included in our next release GSTools 1.1.0. I hope you are OK with that.

Hey Sebastian,
please excuse the late response. Personally, I am quite busy right now and seeing that there has been no response the last 2 weeks, I suppose it's similar for the others. Looking at the code you provided, it seems like an excellent integration and I can't see any reason against including it in your release. While I can't speak for the others, I suspect they feel similarly.
Regarding working together, do you have anything specific in mind? I have a feeling that the project has become kind of a side project for everyone involved so that fresh air is probably helpful :-)
What do you say, @bsmurphy, @rth, @basaks ?
Cheers,
Malte

Hey Malte,
thanks for the nice words. One thing I have in mind is, that your routines could be able to directly take a covariance model from gstools directly, since the presented interface with a provided kwargs dictionary is a bit of a hack. I think it would be nice, if one could provide an instance of our covariance model as a variogram model to your routines, like:
model = Gaussian(dim=2, len_scale=1, anis=0.2, angles=0.5, var=0.5, nugget=0.1)

OK1 = OrdinaryKriging(
    data[:, 0], data[:, 1], data[:, 2],
    variogram_model=model,
)

Then there could be a check, for example, at https://github.com/bsmurphy/PyKrige/blob/a4db3003b0b5688658c12faeb95a5a8b2b14b433/pykrige/ok.py#L216 if the given model is an instance of our model and everything from the input can be overwritten with information from the model and the variogram_model can be set internally as "custom". I think this could be quite convenient.

I created a pull request providing the above mentioned Interface: https://github.com/bsmurphy/PyKrige/pull/125

Thanks for your PR, it is quite nice!

And I think, If you are still working on refactoring your code, It could be a cool thing working together!

We have somewhat a lack of maintainer resources at the moment.
If you have an interest and the availability to improve PyKrige that would be very much appreciated! Personnally, I won't be able to contribute much beyound reviewing some PRs. I got into pykrige in 2015 for a side project, and haven't realy used in my work/outside of work projects since.

@rth and @bsmurphy : If there is interest in joining forces, one idea could be to integrate PyKrige into the GeoStat-Framework. Then we could care about PyKrige together and since the Framework is a GitHub organization, it would be easier for newbies to join the project and create a community maintained package base.
One step in that direction is of course https://github.com/bsmurphy/PyKrige/pull/125. (Sorry for the long delay!)
Maybe we could have a conversation about that. What do you think?
Cheers, Sebastian


Website documentation upload. Sections in progress.

This pull request needs to merge with the olincollege gh-pages branch, not the main branch. If you can fix that, looks good!

Updated the branch to gh-pages.


fix: localize dynamic mixin: fix issue where nested mixin lang terms are not being used

When LocalizeDynamicMixin is used multiple times in an inheritance chain, the top-most localizeConfig always takes precedence.
For example, if you have:
class MyElement extends LocalizeDynamicMixin(LocalizeCoreElement(LitElement)) {
    static localizeConfig() { ... }
}

Then the localizeConfig provided by MyElement will be used everywhere, even inside LocalizeCoreElement -- which defines its own localizeConfig.
The fix: as _getAllLocalizeResources() is called up the inheritance chain, instead of just passing the original top-level localizeConfig, we instead check if a new one is defined at each level and if so use that instead.

Is there anything that should be added to the README about proper order of inheritance?


BicepCLI fails Powershell authentication to ACR on 2012R2

Bicep version
run bicep --version via the Bicep CLI, az bicep version via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep
Bicep CLI version 0.4.1008 (223b8d227a)
Describe the bug
We are unable to authenticate to an ACR with either bicep publish or bicep build on our build servers running 2012r2, when using AzurePowershell credentials (SPN or User account). Using AzureCLI credentials does work. Enable/Disable-AzContextAutosave produces the same result.
To Reproduce
Steps to reproduce the behavior:
import-module -name 'C:\Program Files\WindowsPowerShell\Modules\Az.Accounts\2.7.0\Az.Accounts.psd1' -global
Clear-AzContext -Scope Process
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant

bicep publish names.bicep --target "br:anacr.azurecr.io/test:1.0.0"
bicep : Unhandled exception. Azure.Identity.CredentialUnavailableException: The ChainedTokenCredential failed to
retrieve a token from the included credentials.
    + CategoryInfo          : NotSpecified: (Unhandled excep...ed credentials.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

- Az.Account module >= 2.2.0 is not installed.
- Please run 'az login' to set up account
 ---> System.AggregateException: Multiple exceptions were encountered while attempting to authenticate. (Az.Account
module >= 2.2.0 is not installed.) (Please run 'az login' to set up account)
 ---> Azure.Identity.CredentialUnavailableException: Az.Account module >= 2.2.0 is not installed.
   at Azure.Identity.AzurePowerShellCredential.CheckForErrors(String output)
   at Azure.Identity.AzurePowerShellCredential.RequestAzurePowerShellAccessTokenAsync(Boolean async,
TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken
cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
 ---> (Inner Exception #1) Azure.Identity.CredentialUnavailableException: Please run 'az login' to set up account
   at Azure.Identity.AzureCliCredential.RequestCliAccessTokenAsync(Boolean async, TokenRequestContext context,
CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken
cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)<---
   --- End of inner exception stack trace ---
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext,
CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken
cancellationToken)
   at
Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetRefreshTokenFromCredentialAsync(TokenRequestContext
context, String service, Boolean async, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message,
TokenRequestContext context, String service, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message,
TokenRequestContext context, String service, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryChallengeAuthenticationPolicy.AuthorizeRequestOnChallengeAsyncInternal
(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline,
Boolean async)
   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryBlobRestClient.StartUploadAsync(String name, CancellationToken
cancellationToken)
   at Bicep.Core.RegistryClient.BicepRegistryBlobClient.UploadBlobAsync(Stream stream, CancellationToken
cancellationToken)
   at Bicep.Core.Registry.AzureContainerRegistryManager.PushArtifactAsync(RootConfiguration configuration,
OciArtifactModuleReference moduleReference, StreamDescriptor config, StreamDescriptor[] layers)
   at Bicep.Core.Registry.OciModuleRegistry.PublishModule(RootConfiguration configuration, OciArtifactModuleReference
moduleReference, Stream compiled)
   at Bicep.Core.Registry.ModuleDispatcher.PublishModule(RootConfiguration configuration, ModuleReference
moduleReference, Stream compiled)
   at Bicep.Cli.Commands.PublishCommand.RunAsync(PublishArguments args)
   at Bicep.Cli.Program.RunAsync(String[] args)
   at Bicep.Cli.Program.Main(String[] args)
   at Bicep.Cli.Program.<Main>(String[] args)

Additional context
bicepConfig.json
{
  "analyzers": {
    "core": {
      "enabled": true,
      "verbose": false,
      "rules": {
      }
    }
  },
  "cloud": {
    "currentProfile": "AzureCloud",
    "profiles":{
      "AzureCloud": {
        "resourceManagerEndpoint": "https://management.azure.com",
        "activeDirectoryAuthority": "https://login.microsoftonline.com"
      }
    },
    "credentialPrecedence": [
      "AzurePowerShell",
      "AzureCLI"
    ]
  },
  "moduleAliases": {
    "br": {
      "ldRegistry": {
        "registry": "anacr.azurecr.io"
      },
      "recipes": {
        "registry": "anacr.azurecr.io",
        "modulePath": "bicep/recipes"
      },
      "resources": {
        "registry": "anacr.azurecr.io",
        "modulePath": "bicep/resources"
      },
      "lookups": {
        "registry": "anacr.azurecr.io",
        "modulePath": "bicep/lookups"
      }
    }
  }
}

Hey @justacurley  👋🏼
https://techcommunity.microsoft.com/t5/azure-tools-blog/why-is-az-7-an-important-release-for-azure-powershell/ba-p/3035513
At first look this is likely related to the new release of AZ 7.0.0, which has breaking changes, being a Major version update.
The new module is now using MSGraph, instead of AzureAD, ... the details are in the link above.
So here is a summary of things to test.

Az
Az.Accounts
Az.Resources

7.0.0
2.7.0
5.1.0

6.6.0
2.6.2
4.4.1

For this test, you should be good just delete then add just those 2 individual modules, az.accounts and az.resources.
Then clean up those two modules, shut down powershell etc.
install-module az.resources -RequiredVersion 4.4.1
install-module az.accounts -RequiredVersion 2.6.2

# then the same tests as before
Clear-AzContext -Scope Process
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant

bicep publish names.bicep --target "br:anacr.azurecr.io/test:1.0.0"

Then clean up those two modules, shut down powershell etc.
install-module az.resources -RequiredVersion 2.7.0
install-module az.accounts -RequiredVersion 5.1.0

# then the same tests as before
Clear-AzContext -Scope Process
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant

bicep publish names.bicep --target "br:anacr.azurecr.io/test:1.0.0"

Once we know we can repro only with 2.7.0, we can enable debugging, then capture the logs and go from there.

just to add, it's interesting to see this in the logs, however like I say we can come back to that.
- Az.Account module >= 2.2.0 is not installed.

Unfortunately we've repro'd the issue with the older versions =P
import-module -name 'C:\Program Files\WindowsPowerShell\Modules\Az.Accounts\2.6.2\Az.Accounts.psd1' -global -force | Out-Null
import-module -name "C:\Program Files\WindowsPowerShell\Modules\Az.Resources\4.4.1\Az.Resources.psd1" -global -force | Out-Null
gmo az.resources
gmo az.accounts

Clear-AzContext -Scope Process | Out-Null
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue | Out-Null
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud | Out-Null
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant | Out-Null

bicep publish D:\names.bicep --target "br:ldseabasstest.azurecr.io/test:1.0.0"

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     4.4.1      Az.Resources                        {Add-AzADGroupMember, Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzADAppCredential...}
Script     2.6.2      Az.Accounts                         {Add-AzEnvironment, Clear-AzContext, Clear-AzDefault, Connect-AzAccount...}

bicep : Unhandled exception. Azure.Identity.CredentialUnavailableException: The ChainedTokenCredential failed to retrieve a token from the included credentials.
At line:8 char:1
+ bicep publish D:\names.bicep --target "br:ldseabasstest.azurecr.io/te ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Unhandled excep...ed credentials.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

- Az.Account module >= 2.2.0 is not installed.
- Please run 'az login' to set up account
 ---> System.AggregateException: Multiple exceptions were encountered while attempting to authenticate. (Az.Account module >= 2.2.0 is not installed.) (Please run 'az
login' to set up account)
 ---> Azure.Identity.CredentialUnavailableException: Az.Account module >= 2.2.0 is not installed.
   at Azure.Identity.AzurePowerShellCredential.CheckForErrors(String output)
   at Azure.Identity.AzurePowerShellCredential.RequestAzurePowerShellAccessTokenAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
 ---> (Inner Exception #1) Azure.Identity.CredentialUnavailableException: Please run 'az login' to set up account
   at Azure.Identity.AzureCliCredential.RequestCliAccessTokenAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)<---
   --- End of inner exception stack trace ---
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetRefreshTokenFromCredentialAsync(TokenRequestContext context, String service, Boolean async,
CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message, TokenRequestContext context, String service, Boolean
async)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message, TokenRequestContext context, String service, Boolean
async)
   at Bicep.Core.RegistryClient.ContainerRegistryChallengeAuthenticationPolicy.AuthorizeRequestOnChallengeAsyncInternal(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryBlobRestClient.StartUploadAsync(String name, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.BicepRegistryBlobClient.UploadBlobAsync(Stream stream, CancellationToken cancellationToken)
   at Bicep.Core.Registry.AzureContainerRegistryManager.PushArtifactAsync(RootConfiguration configuration, OciArtifactModuleReference moduleReference, StreamDescriptor
config, StreamDescriptor[] layers)
   at Bicep.Core.Registry.OciModuleRegistry.PublishModule(RootConfiguration configuration, OciArtifactModuleReference moduleReference, Stream compiled)
   at Bicep.Core.Registry.ModuleDispatcher.PublishModule(RootConfiguration configuration, ModuleReference moduleReference, Stream compiled)
   at Bicep.Cli.Commands.PublishCommand.RunAsync(PublishArguments args)
   at Bicep.Cli.Program.RunAsync(String[] args)
   at Bicep.Cli.Program.Main(String[] args)
   at Bicep.Cli.Program.<Main>(String[] args)

okay, that is good.
When you test, can you simply use the module name to import them, not the full path.
They should be available in the $env:psmodulepath to import without the full path anyway.

Same with the latest versions...
import-module -name Az.Accounts -global -force | Out-Null
import-module -name Az.Resources -global -force | Out-Null
gmo az.resources
gmo az.accounts

Clear-AzContext -Scope Process | Out-Null
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue | Out-Null
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud | Out-Null
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant | Out-Null

bicep publish names.bicep --target "br:anacr.azurecr.io/test:1.0.0"

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     5.1.0      Az.Resources                        {Export-AzResourceGroup, Export-AzTemplateSpec, Get-AzDenyAssignment, Get-AzDeployment...}
Script     2.7.0      Az.Accounts                         {Add-AzEnvironment, Clear-AzContext, Clear-AzDefault, Connect-AzAccount...}

bicep : Unhandled exception. Azure.Identity.CredentialUnavailableException: The ChainedTokenCredential failed to retrieve a token from the included credentials.
At line:6 char:1
+ bicep publish D:\names.bicep --target "br:anacr.azurecr.io/te ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Unhandled excep...ed credentials.:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

- Az.Account module >= 2.2.0 is not installed.
- Please run 'az login' to set up account
 ---> System.AggregateException: Multiple exceptions were encountered while attempting to authenticate. (Az.Account module >= 2.2.0 is not installed.) (Please run 'az login' to set up account)
 ---> Azure.Identity.CredentialUnavailableException: Az.Account module >= 2.2.0 is not installed.
   at Azure.Identity.AzurePowerShellCredential.CheckForErrors(String output)
   at Azure.Identity.AzurePowerShellCredential.RequestAzurePowerShellAccessTokenAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzurePowerShellCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.AzurePowerShellCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
 ---> (Inner Exception #1) Azure.Identity.CredentialUnavailableException: Please run 'az login' to set up account
   at Azure.Identity.AzureCliCredential.RequestCliAccessTokenAsync(Boolean async, TokenRequestContext context, CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.CredentialDiagnosticScope.FailWrapAndThrow(Exception ex, String additionalMessage)
   at Azure.Identity.AzureCliCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.AzureCliCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)<---
   --- End of inner exception stack trace ---
   at Azure.Identity.ChainedTokenCredential.GetTokenImplAsync(Boolean async, TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Azure.Identity.ChainedTokenCredential.GetTokenAsync(TokenRequestContext requestContext, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetRefreshTokenFromCredentialAsync(TokenRequestContext context, String service, Boolean async, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message, TokenRequestContext context, String service, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryRefreshTokenCache.GetAcrRefreshTokenAsync(HttpMessage message, TokenRequestContext context, String service, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryChallengeAuthenticationPolicy.AuthorizeRequestOnChallengeAsyncInternal(HttpMessage message, Boolean async)
   at Azure.Core.Pipeline.BearerTokenAuthenticationPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RedirectPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Azure.Core.Pipeline.RetryPolicy.ProcessAsync(HttpMessage message, ReadOnlyMemory`1 pipeline, Boolean async)
   at Bicep.Core.RegistryClient.ContainerRegistryBlobRestClient.StartUploadAsync(String name, CancellationToken cancellationToken)
   at Bicep.Core.RegistryClient.BicepRegistryBlobClient.UploadBlobAsync(Stream stream, CancellationToken cancellationToken)
   at Bicep.Core.Registry.AzureContainerRegistryManager.PushArtifactAsync(RootConfiguration configuration, OciArtifactModuleReference moduleReference, StreamDescriptor config, StreamDescriptor[] layers)
   at Bicep.Core.Registry.OciModuleRegistry.PublishModule(RootConfiguration configuration, OciArtifactModuleReference moduleReference, Stream compiled)
   at Bicep.Core.Registry.ModuleDispatcher.PublishModule(RootConfiguration configuration, ModuleReference moduleReference, Stream compiled)
   at Bicep.Cli.Commands.PublishCommand.RunAsync(PublishArguments args)
   at Bicep.Cli.Program.RunAsync(String[] args)
   at Bicep.Cli.Program.Main(String[] args)
   at Bicep.Cli.Program.<Main>(String[] args)

just an update on this thread for now.
Tested with old and new AZ Modules, Tested with old and new Bicep.exe.
The issue is across a fleet of Server 2012 R2 build servers, Issue starting on past Friday 10th, assume after the AZ module upgrade to 7.0.0. Assume some corruption of the token cache, however not evidence of this so far.
enabling Bicep Tracing shows:
Exception: Azure.Identity.CredentialUnavailableException (0x80131500): Az.Account module >= 2.2.0 is not installed.

As shown below this is the same error as when the AZ CLI is not logged in.

So it appears that it cannot find any cached credentials, perhaps the specific error message is just misleading about 2.2.0

Bicep CLI version 0.4.1124 (66c84c8ee5)

C:\Users\foo\Desktop\bicep-win-x64.exe publish D:\names.bicep --target "br:foo.azurecr.io/test:1.0.0"

TRACE: Building semantic model for file:///D:/names.bicep
TRACE: Azure-Core: [Informational] Request [c6e7a553-a4fb-4d47-b07b-e64018aa2176] POST https://foo.azurecr.io/v2/test/blobs/uploads/ client assembly: Azure.Containers.ContainerRegistry
TRACE: Azure-Core: [Warning] Error response [c6e7a553-a4fb-4d47-b07b-e64018aa2176] 401 Unauthorized (00.7s)
TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken invoked. Scopes: [ https://management.azure.com/.default ] ParentRequestId: c6e7a553-a4fb-4d47-b07b-e64018aa2176
TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken was unable to retrieve an access token. Scopes: [ https://management.azure.com/.default ] ParentRequestId: c6e7a553-a4fb-4d47-b07b-e64018aa2176 Exception: Azure.Identity.CredentialUnavailableException (0x80131500): Az.Account module >= 2.2.0 is not installed.
TRACE: Azure-Identity: [Informational] AzureCliCredential.GetToken invoked. Scopes: [ https://management.azure.com/.default ] ParentRequestId: c6e7a553-a4fb-4d47-b07b-e64018aa2176
TRACE: Azure-Identity: [Informational] AzureCliCredential.GetToken was unable to retrieve an access token. Scopes: [ https://management.azure.com/.default ] ParentRequestId: c6e7a553-a4fb-4d47-b07b-e64018aa2176 Exception: Azure.I dentity.CredentialUnavailableException (0x80131500): Please run 'az login' to set up account

I believe deleting the Azure context and also the MSAL cache did not resolve the issue.

rename-item $home\.Azure\ .Azure_OLD -WhatIf
rename-item $env:LOCALAPPDATA\.IdentityService\msal.cache msal.cache_OLD -WhatIf

However logging in with AZ Cli works fine and this is the workaround that is in place at this time.

@brwilkinson - note that the Azure.Identity module doesn't look for cached credentials directly - it actually loads and invokes the AzPwsh module to obtain credentials:
https://github.com/Azure/azure-sdk-for-net/blob/904813957ebdfaae39cb9096a9c5b01c58141b94/sdk/identity/Azure.Identity/src/AzurePowerShellCredential.cs#L200-L240
If my understanding is correct, the error message does appear relevant - seems like perhaps the module has a dependency on a particular command which is not available.

Thanks @anthony-c-martin
Below is the code block from link.
@justacurley i am sure we have tested these, with your account, however explicitly testing this may be helpful.
 $ErrorActionPreference = 'Stop'
 [version]$minimumVersion = '2.2.0'

 $m = Import-Module Az.Accounts -MinimumVersion $minimumVersion -PassThru -ErrorAction SilentlyContinue

 if (! $m) {{
     Write-Output '{AzurePowerShellNoAzAccountModule}'
     exit
 }}

 $token = Get-AzAccessToken -ResourceUrl '{resource}'{tenantIdArg}

 $x = $token | ConvertTo-Xml
 return $x.Objects.FirstChild.OuterXml

If it's not successful we can test with:
$debugpreference = "continue"
Plus your service account.
Seems like the $env:psmodulepath is the only system configuration needed for this to be discovered.
Please can you also execute that value in the same script output.

One more item, it looks like it runs powershell with no profile. So we should test that.
                powershellExe = "powershell -NoProfile -NonInteractive -EncodedCommand";

@brwilkinson here is that test without debugging
Disable-AzContextAutoSave
logout-azaccount
logout-azaccount
Clear-AzContext -Scope Process
Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Clear-AzContext -Force
Connect-AzAccount -ServicePrincipal -Tenant $tenant -Credential $Credential -Environment AzureCloud
Set-AzContext -SubscriptionId $Subscription -Tenant $tenant

$command = @'
$ErrorActionPreference = 'Stop'
[version]$minimumVersion = '2.2.0'
$m = Import-Module Az.Accounts -MinimumVersion $minimumVersion -PassThru -ErrorAction SilentlyContinue
if (! $m) {{
    Write-Output "Can't find az.accounts >= 2.2.0"
    exit
}}
$token = Get-AzAccessToken -ResourceUrl 'https://management.azure.com/' -TenantId 'xxxx'
$x = $token | ConvertTo-Xml
return $x.Objects.FirstChild.OuterXml
'@

$encodedcommand = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($command))

cmd /c "powershell -NoProfile -NonInteractive -EncodedCommand $Encodedcommand"

The result is Get-AzAccessToken throwing
Get-AzAccessToken : Run Connect-AzAccount to login.
At line:8 char:10
+ $token = Get-AzAccessToken -ResourceUrl 'https://management.azure.com ...
+          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Get-AzAccessToken], PSInvalidOperationExcepti
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.GetAzureRmAccessTokenCommand

Adding $debugPreference='continue' to the top of $command, we get this
DEBUG: Sought all Az modules and got latest version 0.0.0
DEBUG: 8:36:50 AM - GetAzureRmAccessTokenCommand begin processing with ParameterSet 'ResourceUrl'.
Get-AzAccessToken : Run Connect-AzAccount to login.
At line:9 char:10
+ $token = Get-AzAccessToken -ResourceUrl 'https://management.azure.com ...
+          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Get-AzAccessToken], PSInvalidOperationException
    + FullyQualifiedErrorId : Microsoft.Azure.Commands.Profile.GetAzureRmAccessTokenCommand

Running the above script with Enable-AzContextAutoSave to cache the credentials DOES return an access token, but bicep publish still returns the same error =[
$env:BICEP_TRACING_ENABLED = $true
 bicep publish D:\names.bicep --target "br:ancr.azurecr.io/test:1.0.0"
TRACE: Building semantic model for file:///D:/names.bicep
TRACE: Azure-Core: [Informational] Request [eb669f8f-a96b-426c-a182-17b94b00b213] POST https://anacr.azurecr.io/
v2/test/blobs/uploads/
client assembly: Bicep.Core.RegistryClient
TRACE: Azure-Core: [Warning] Error response [eb669f8f-a96b-426c-a182-17b94b00b213] 401 Unauthorized (01.0s)

TRACE: Azure-Identity: [Informational] AzureCliCredential.GetToken invoked. Scopes: [ https://management.azure.com/.defa
ult ] ParentRequestId: eb669f8f-a96b-426c-a182-17b94b00b213
TRACE: Azure-Identity: [Informational] AzureCliCredential.GetToken was unable to retrieve an access token. Scopes: [ htt
ps://management.azure.com/.default ] ParentRequestId: eb669f8f-a96b-426c-a182-17b94b00b213 Exception: Azure.Identity.Cre
dentialUnavailableException (0x80131500): Please run 'az login' to set up account
TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken invoked. Scopes: [ https://management.azure.co
m/.default ] ParentRequestId: eb669f8f-a96b-426c-a182-17b94b00b213
TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken was unable to retrieve an access token. Scopes
: [ https://management.azure.com/.default ] ParentRequestId: eb669f8f-a96b-426c-a182-17b94b00b213 Exception: Azure.Ident
ity.CredentialUnavailableException (0x80131500): Az.Account module >= 2.2.0 is not installed.
Unhandled exception. Azure.Identity.CredentialUnavailableException: The ChainedTokenCredential failed to retrieve a toke
n from the included credentials.
- Please run 'az login' to set up account
- Az.Account module >= 2.2.0 is not installed.

@justacurley Thanks for testing/confirming all of that.
Just to confirm, you are currently (temporarily) unblocked on this by setting the az cli login for the bicep publish?
Can you share you share the settings on your pipeline task? Are you using ADO Pipeline or GH Workflow ?
  steps:
  - task: AzurePowerShell@5
    inputs:
      azureSubscription: ${{ parameters.SP }}-G0
      ScriptType: 'FilePath'
      FailOnStandardError: true
      azurePowerShellVersion: 'LatestVersion'
      # preferredAzurePowerShellVersion: 6.0.0
      pwsh: true

We had tested with WMF (PowerShell 5.1), however I assume that pwsh is installed and that the pipeline is configured to use pwsh?
cmd /c "pwsh -NoProfile -NonInteractive -EncodedCommand $Encodedcommand"

So perhaps given this is a self hosted agent, pwsh is finding an older version of AZ in the powershell 7 specific directories and not finding the newer AZ in WindowsPowerShell directories ?
e.g.
this:
cmd /c "powershell -NoProfile -NonInteractive -command {$env:psmodulepath}"

compared to:
cmd /c "pwsh -NoProfile -NonInteractive -command {$env:psmodulepath}"

Adding the link to this:
https://github.com/Azure/azure-sdk-for-net/blob/904813957ebdfaae39cb9096a9c5b01c58141b94/sdk/identity/Azure.Identity/src/AzurePowerShellCredential.cs#L103
Perhaps pwsh 7 was recently installed on these servers and that is why it is being picked up now by default?
If that is the case, I am not sure I see a setting to set UseLegacyPowerShell. It appears to fail back if an exception is thrown when it cannot find pwsh.
            try
            {
                AccessToken token = await RequestAzurePowerShellAccessTokenAsync(async, requestContext, cancellationToken).ConfigureAwait(false);
                return scope.Succeeded(token);
            }
            catch (Win32Exception ex) when (ex.NativeErrorCode == ERROR_FILE_NOT_FOUND && RuntimeInformation.IsOSPlatform(OSPlatform.Windows))
            {
                UseLegacyPowerShell = true;
                try
                {
                    AccessToken token = await RequestAzurePowerShellAccessTokenAsync(async, requestContext, cancellationToken).ConfigureAwait(false);
                    return scope.Succeeded(token);
                }
                catch (Exception e)
                {
                    throw scope.FailWrapAndThrow(e);
                }
            }
            catch (Exception e)
            {
                throw scope.FailWrapAndThrow(e);
            }

I was unaware pwsh was installed at all on these build servers. I checked, and it's PS6.x
The pipeline is not configured to use pwsh, but if UseLegacyPowershell = false then I guess we'll have to for now.
I installed pwsh 7.2.1 and bicep.exe is now able to publish. I will make an issue/pr for azure.identity to have that encodedCommand print the powershell version being run when it throws.
Thanks you @brwilkinson & @anthony-c-martin  👏 🙏
TRACE: Building semantic model for file:///D:/names.bicep
TRACE: Azure-Core: [Informational] Request [2723c896-81c2-453c-8cb8-ca29363ea09c] POST https://anacr.azurecr.io/v2/test/blobs/uploads/
client assembly: Bicep.Core.RegistryClient
TRACE: Azure-Core: [Warning] Error response [2723c896-81c2-453c-8cb8-ca29363ea09c] 401 Unauthorized (00.9s)

TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken invoked. Scopes: [ https://management.azure.com/.default ] ParentRequestId: 2723c896-81c2-453c-8cb8-ca29363ea09c
TRACE: Azure-Identity: [Informational] AzurePowerShellCredential.GetToken succeeded.
If you have any interest, in me following up with the sdk team to ask about making 'UseLegacyPowershell' a user configurable setting, let me know?
Personally I am all in on pwsh however would be happy to do that follow up on behalf of others, if anyone is interested?

I was planning on a PR for something like
...
 if (! $m) {{
     Write-Output '{AzurePowerShellNoAzAccountModule}'
     $PSVersion = 'PSVersion: {0}' -f $PSVersionTable.PSVersion.ToString()
     Write-Output $PSVersion
     exit
 }}
...

I'm not sure what that will look like on the other side yet, but if it could print out  PSVersion: <IP_ADDRESS> it will save the next person a few days of troubleshooting. If UseLegacyPowershell makes more sense to more people then that's the way to go.

Okay, if you open an issue over there us know. We can discuss further over there.
I think that output is parsed for the error message, so you may need to implement the extra logging outside of the powershell, or else perhaps add an alternate exception or something similar i.e. 1 exception for this error in pwsh and another for powershell. e.g. AzurePowerShellNoAzAccountModule versus AzurePWSHNoAzAccountModule?!

Just to be clear though -- this isn't a Server 2012 issue, right?
The problem occurs when you have pwsh but aren't using it, or possibly whenever the user doesn't cache credentials outside the process?
Shouldn't bicep have it's own authentication option, instead of depending strictly on pre-cached credentials from the other tools (which might not even be in use)?

Just to be clear though -- this isn't a Server 2012 issue, right?

No it's not operating system specific. Unless perhaps there was something on your side, e.g. all 2012 R2 machines had the pwsh v6.0 published/deployed Etc. So there could have been some targeting there (by OS) however nothing specific on the technology side of the OS.
The Container Registry is using 'DefaultAzureCredential' as part of Azure.Identity to authenticate. This is combined with the Bicep config file.
DefaultAzureCredential
https://docs.microsoft.com/en-us/dotnet/api/azure.identity.defaultazurecredential?view=azure-dotnet
BicepConfig
https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config-modules#credentials-for-restoring-modules
Notice the docs show the following configuration options (from within the bicepconfig.json)
The available credentials (that you can enable in the config file) are:

AzureCLI
AzurePowerShell
Environment
ManagedIdentity
VisualStudio
VisualStudioCode

This works nicely for different scenarios, however if you have an option enabled and you are not logged in it will fail.
The issue is that the 'AzurePowerShell' option is not very elegant at the moment, it tries pwsh first, if it finds it (any version) installed (then fails when it cannot find the az.accounts in the module path for that version). It only drops/fails back to powershell.exe if pwsh is not installed at all.
The ideal solution on the SDK side would be one of the following:

Have AzurePowerShell and AzurePWSH as 2 distinct options, instead of grouping them together as a single option.

The executables are different and the Module paths/installation is different, so they really should be discrete options.

Improve failback to PowerShell if pwsh fails or at least improve the messaging on the current actions.

As a side note: pwsh version 6 is no longer supported, so it would also be recommended to clean that up on your side. However this same issue could have also resulted from having pwsh 7 installed, which is supported.


Replace ':' in series_name and title template variables

Describe the bug
I am using series_name template variable to put the downloaded episode in a folder with series_name name.
When the name contains the character ':' in the file manager I am not seeing the actual name but some gibberish(like this "DCIRWL~N"). When using the command like I can see that the name is ok just the display in the file browser is wrong.
Context: the download happens on a server and I am looking at the files that are shared through samba - that's what is most likely responsible for the problem - when I made the same folder name locally it displayed correctly.
I have only seen this for the series_name variable but I am guessing it would apply for the title also and maybe other variables I am not aware of.
To Reproduce
Download any series  that contain ':' in the name with this in the command line
 -o "{series_name}/[S{season_number}E{episode_number}] {title}.mkv"

and access it through samba on a linux machine
Expected behavior
Folder name displays correctly
Client (please complete the following information):

OS: Arch Linux for both the server and client - client is with KDE DE
Version: 3.2.5

Additional context
Add any other context about the problem here.

--universal-output is probably what you need

What is "--universal-output" and how it's used - I don't see it in the crunchy-cli description

It basically sanitizes the file outputs for windows, which is the most restrictive. In your case it will remove colons from the output file.

Gotcha, my bad

Ok thank you. I'll wait for the next release.

The flag is now available in v3.3.0


FIX: Add channel ID attribute to chat quotes

We have run across various complications when trying to
link to a channel by channel title (see /t/66638 and
https://github.com/discourse/discourse-chat/pull/857 for
examples) so instead we are just going to add a channel
ID to the chat quotes instead for easier linking.
This commit also improves DM channel titles for chat quotes,
which were not taken into account in the original design,
but was later allowed in 1f10fc6c4cf5642d21419eff30dc986d0cd33a7c.

@martin-brennan test failure looks legit

Thanks @jjaffeux forgot to update again after last change, should go through this time (thanks for approval too :+1: )


Limit the size of images in Marketplace

Makes images smaller when uploaded from the UI and checks the image size when adding a product from the API.

LGTM


Disabled default 60 mins Azure Pipelines timeout

With the disabled timeout, the current actual timeout is 6 hours.

We have experienced builds which did freeze, 6 hours would be a long time if nobody notice it directly. I'm wondering if we should set a default value of 2 hours or so? Should be enough for most jobs. We currently have 50 & 60 Minutes on Travis and AppVeyor per Job.

Yep, maybe 2 hours is better.

Fixed via 5e23f1e9813b7896ece616f350086536537dfb84


Fix for copy example input files failing on Linux

This fixes errors that occur when trying to use the SteamVR Input window for the first time on Linux. Errors occur in the original code where it complains about the copy failing, because it is attempting to copy the file onto itself.
This change removes the expectation of a Windows like file path. I haven't tested it on Windows, just Linux, but it did copy the files over correctly.

Thanks! Took this pull and put it in the latest beta: https://github.com/ValveSoftware/steamvr_unity_plugin/releases


ci: add mergify

:tada: This PR is included in version 2.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


LO2H-107: Upgrade hapi-fhir and upgrade FHIR version to R5

Hi Amy, I am not sure exactly if we need to be compatible with multiple versions of FHIR. I think it is fine if we can basically meet the requirements of Vulcan. But the README should indicate if we ONLY support version 5.

Hi Peter. This library doesn't actually talk to any servers, so the upgrade in this pull request is really about making sure that the Observations passed in are structurally compatible for R5. In general it is easier to "upgrade" an Observation than to downgrade it. The SMART on FHIR app using this library might communicate with an earlier versioned FHIR server. If so, it takes on the job of upgrading the Observation structure to R5 in order to use this library and convert the Observation to HPO. We could certainly support other FHIR versions directly in this library, but I prefer to leave that to the consumer with conversion being a relatively straightforward exercise using the HAPI libraries.


refactor: Add function to make all column ids in a tree unique and sequential

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

Could you please add some tests to increase the test coverages on these core files. Thanks! The following link is the current coverage status: https://fusion2.corp.google.com/ci/kokoro/prod:bigframes%2Fpresubmit%2Fpresubmit/activity/88a8d1da-2043-4a7a-8ae8-0b91d7e51c84/log

increasing code coverage is definitely a goal, however the code in this PR is covered (minus assert code that should never hit).


Undo on EDIT commands adding a new tag is broken

Unable to UNDO and remove the recently added tag during EDIT command

Fixed in #100


.NET Core 3.1 not available on 18.04

Experiencing publishing issues on the repo side. An incident response ticket has been opened with that team and we'll keep this issue updated as we learn more.
referencing the announcement issue for visibility - https://github.com/dotnet/core/issues/3950

Linux repo team is investigating - no eta yet.

18.04 tested good. Should be good to go.


feat/make some dependencies optional

unstructured has many dependencies and usually, we don't want all of these features the package provides.
Making some dependencies optional (for example, nltk, python-pptx and etc ) will keep the package small, speeding up the application in CI, and reducing memory and disk usage in production.
$poetry show unstructured
 name         : unstructured
 version      : 0.6.6
 description  : A library that prepares raw documents for downstream ML tasks.

dependencies
 - argilla *
 - certifi >=2022.12.07
 - lxml *
 - markdown *
 - msg-parser *
 - nltk *
 - openpyxl *
 - pandas *
 - pdfminer.six *
 - pillow *
 - pypandoc *
 - python-docx *
 - python-magic *
 - python-pptx *
 - requests *

Related issue #610

Thanks @elonzh - tracking this one and the other issue you linked as well.


Expand integer constant expressions as macros

Currently macro and macro-rec must expand directly to non-function symbols to be used on the LHS of rules. But often times, macros are expandable to constant expressions with some simple evaluations.
Examples are #pow256 => 2 ^ 256 in EVM, and _minutes => 60 * _ in MKR MCD.
It would be nice if in these special cases, we could have the frontend evaluate the actual integer expression directly when expanding the macro.

This should largely be subsumed by constant folding over the rules in a semantics. Closing for now.


Automatic Idp Key Rotation Handling

Story
As a gluu admin
I want remote idp keys to be handled automatically
so that I save time and money
Depends on

[x] Generate SP MEtadata #30
[x] Get metadata from url #11

Description
Daily cron job to update remote idp keys if public metadata url is available.

added description:
Daily cron job to update remote idp keys if public metadata url is available.


Support using Mock as mixin

Is your feature request related to a problem? Please describe.
I'm using mocktail in conjunction with getx and want do use the Mock class as a mixin:
class MockBluetoothService extends GetxService
    with Mock
    implements BluetoothService {}

However, the prefer_mixin rule tells me that Mock should be a mixin, not a class. I've disabled the rule for now.
Describe the solution you'd like
It would be awesome if mocktail provided a MockMixin or similar that was tailor-made to be used as a mixin.
Describe alternatives you've considered
Alternatives are to disable the prefer_mixin rule. I don't think I can use GetxService as a mixin.

Closing for now since it's been a while and it doesn't appear there are any actionable next steps. Feel free to comment if you have any further questions and I'm happy to continue the conversation 👍

Thanks for the response, I didn't get around to testing it but assume that your answer will indeed fix my problem.

In my situation, I want to mock mixing class generated by Riverpod:
class MockNewUser extends _$Reviews with Mock implements Reviews {}
I am getting this error : Mixin can only be applied to class.


Fix hot reloading when modifying pages from routes.

Using react-static v5.9.8, hot reloading only works on App.js. Adding the line below in .babelrc fix it. I only tested on theses examples, but this problem might happen in others.
plugins": ["react-hot-loader/babel"]
See https://github.com/nozzle/react-static/issues/725

This is very strange, because the react-static/babel-preset.js has the plugin included already.

I know this is not a fix for the real problem, but I think the examples should just work after downloading for people that are testing react-static. Feel free to ignore and close it. No hard feelings lol

This is v5 and will soon be outdated, so it's not a huge priority. But at the same time, I want people who use it until v6 to be happy.
I will merge this PR if you add the changes to all the remaining example directories. Thoughts?

I can do that.

Nice! Thanks 😄


add a rolling average 7 day graph, the same as FHM

Was planning to add rolling 7 day avg of reported deaths. Is that what FHM do or is their actual deaths?

they do daliy and rolling on the same numbers, labratory confirmed covid-19 death from FHM, socialstyrelsen has numbers for all death from covid-19, if the doctor writes it in the death certificate, not just from testing, they say its about 10% more

Thanks! I'm thinking about it. But would maybe find it more interesting to use reported deaths. Just need to find some time to do the update .)

Added both a version now with three different lines. What do you think?


OpenSearchVectorStore similaritySearch Metadata filtering not working for exact match

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
const docs = [
      new Document({
        metadata: { user: "U12345-1234" },
        pageContent: "Amazon Simple Storage Service (Amazon S3) is a cloud storage service that allows users to store and retrieve data of any amount from anywhere.",
      }),
      new Document({
        metadata: { user: "U12345-5678" },
        pageContent: "Amazon Elastic Compute Cloud (Amazon EC2) provides on-demand, scalable computing capacity in the Amazon Web Services (AWS) Cloud.",
      }),
    ];

const vectorStore = await OpenSearchVectorStore.fromDocuments(docs, embeddings, {
        client: client,
        indexName: 'my-index',
        service: 'aoss'
      });

const query = "What is S3?";
const k = 5; // Number of results to retrieve
const filter = {
  user: "U12345-1234"
};

// Returns no documents
const results = await vectorStore.similaritySearch(query, k, filter);

### Error Message and Stack Trace (if applicable)

_No response_

### Description

OpenSearchVectorStore similarity search metadata filtering not returning any documents for an exact match of the specified user field in the document metadata.

### System Info

AWS Lambda running Node.js 20.x

@dosu When i run this, i still don't get any documents back

The above code does not work as "term" queries no longer seem to return results from OpenSearch. Is there any way to bypass this and pass in my own filter query?


Getting error dial tcp: no such host

Required check list:

[x] I'm gonna mark the checkboxes like this.
[x] I didn't find in the Create Go App CLI repository's issues section similar bug.
[x] I understand, that the Create Go App CLI is Open Source and not-for-profit product.
[x] This is not about third-party project, framework, package or technology.

My environment:

OS (Darwin mofodoxs-MacBook-Pro-13.local 20.6.0 Darwin Kernel Version 20.6.0: Mon Aug 30 06:12:21 PDT 2021; root:xnu-7195.141.6~3/RELEASE_X86_64 x86_64):
Golang (go version go1.17.2 darwin/amd64):
Create Go App CLI (cgapp version 3.1.1):

Describe the bug:
How do I run the backend application. I've followed the instructions from the README.md in the backend folder but I kept getting this error:
migrate -path /Users/mofodox/Documents/projects/cgapptest/backend/platform/migrations -database "postgres://postgres:password@cgapp-postgres/postgres?sslmode=disable" up
error: dial tcp: lookup cgapp-postgres on <IP_ADDRESS>:53: no such host
make: *** [migrate.up] Error 1

Steps to reproduce the behavior:

Run the cgapp create command
Choose the options available
Rename the .env.example to .env (backend folder)
Installed golang-migrate, gosec, swagger
Run the application using the make command: make docker.run

Thank you!

Hi @koddr,
Yes the Docker is running on my machine when I tried to run the backend server running ‘make docker.run’ command


Luxor 2.18

PR Checklist
If you are contributing to Javis.jl, please make sure you are able to check off each item on this list:

[x] Did I update CHANGELOG.md with whatever changes/features I added with this PR?
[x] Did I make sure to only change the part of the file where I introduced a new change/feature?
[x] Did I cover all corner cases to be close to 100% test coverage (if applicable)?
[x] Did I properly add Javis dependencies to the Project.toml + set an upper bound of the dependency (if applicable)?
[x] Did I properly add test dependencies to the test directory (if applicable)?
[x] Did I check relevant tutorials that may be affected by changes in this PR?
[x] Did I clearly articulate why this PR was made the way it was and how it was made?

How did you address these issues with this PR? What methods did you use?
Due to my bugfix in Luxors simplify method (https://github.com/JuliaGraphics/Luxor.jl/releases/tag/v2.18.0) our test cases for morphing failed. I can't see any change with my eyes so updated the reference images.
I think it makes sense to still allow Luxor v2.12 for now as everything works just fine and I don't want to force people to update to Luxor v2.18. We should just keep it in mind.
What do you think @TheCedarPrince ?

Codecov Report

Merging #455 (622ad34) into master (bc65d7a) will decrease coverage by 0.01%.
The diff coverage is n/a.

:exclamation: Current head 622ad34 differs from pull request most recent head 1ad10b8. Consider uploading reports for the commit 1ad10b8 to get more accurate results

@@            Coverage Diff             @@
##           master     #455      +/-   ##
==========================================
- Coverage   96.26%   96.25%   -0.02%
==========================================
  Files          36       36
  Lines        1633     1628       -5
==========================================
- Hits         1572     1567       -5
  Misses         61       61

Impacted Files
Coverage Δ

src/Javis.jl
95.96% <ø> (-0.09%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7bb323...1ad10b8. Read the comment docs.


Bump systemd-boot to 257

They changed the paths for some reason

Lets block it until we release a patch as to not bring it already. for 3.6.0


Create a flattened keystore that simplifies key access/filtering

this is a duplicate of https://github.com/docker/notary/issues/502.  I'll close this one since there's more history there, and make sure that issue is on our milestone.


Multiple package launch makes Sick_safetyscanners2_node-1 crash

Hi,
We have been struggling with an issue regarding Sick_safetyscanners2 node. Standalone only launching Sick_safetyscanners2 30 times has no issues, but using our launch file running multiple nodes after 16 times, Sick_safetyscanners2 gives process has died error with exit code -11. The weird part is that the error shows up after the Communication to Sensor set up has already occured
[sick_safetyscanners2_node-1] [INFO]: Command Method Acknowledged. [sick_safetyscanners2_node-1] [INFO] [1621334701.382357271] [testing.sick_safetyscanners2_node]: Communication to Sensor set up [sick_safetyscanners2_node-1] [INFO] [1621334701.382614487] [testing.sick_safetyscanners2_node]: Reading Type code settings [sick_safetyscanners2_node-1] [INFO]: Command Variable Acknowledged. [sick_safetyscanners2_node-1] [INFO]: Type Code: NANS3-CAAZ30AN1P04
Only missing INFO is the following when this error occurs:
[sick_safetyscanners2_node-1] [INFO] [1621336333.044491863] [serena.sick_safetyscanners2_node]: Node Configured and running
The full error code:
[ERROR] [sick_safetyscanners2_node-1]: process has died [pid 2355821, exit code -11, cmd '/home/somagallai/user/testing/install/sick_safetyscanners2/lib/sick_safetyscanners2/sick_safetyscanners2_node --ros-args -r __node:=sick_safetyscanners2_node -r __ns:=/testing --params-file /tmp/launch_params_3o1wk_jy'].
Is there a way to see a more explicit error description what could be causing the issue?

Hi,
this is odd behaviour. To Further inspect this build the package with Debug Information from source. So either use RelWithDebInfo or Debug
colcon build <other_args> --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo

Afterwards you are able to start the node with gdb. This is nicely described in:
https://navigation.ros.org/tutorials/docs/get_backtrace.html
This allows you to get a stack trace and see where the error is occurring.

Hi,
I have tested our launch file using gdb, thank you for the instructions! Using gdb I was not able to make Sick_safetyscanners2 crash 40+ tries. Without gdb, but using ros2 launch -debug argument I was able to catch that when Sick_safetyscanners2 crashes the order of methods called are messed up.
When Sick_safetyscanners2 works as expected the method calls are the following:

Process start
Initializing
Parameters configuration
Command method Acknowledged
Communication to Sensor Set Up
Reading Type Code settings
Command variable Acknowledged
Type code
Command Method Acknowledged
Node configured and running

When it crashes the following method call order has been seen:
crash1:

Process start
Initializing
Parameters configuration
Command method Acknowledged
Command variable Acknowledged
Type code
Communication to Sensor Set Up
Reading Type Code settings
Process has died

crash2:

Process start
Initializing
Parameters configuration
Communication to Sensor Set Up
Reading Type Code settings
Command method Acknowledged
Command variable Acknowledged
Type code
Process has died

Hm okay, that looks like some sort of racing condition might be happening. IS there anything special in your launch file or your setup? And do you have high latencies between sensor and driver? I will try to have a look into it, but since I haven't experienced the problem myself I might not be able to recreate it. So any insights would be helpful

Are there any new insights? Did you find a solution for the problem?

Are there any new insights? Did you find a solution for the problem?

It seems as PR #11 seems to do the trick, we have been using it for a while and the issue has not arose since then.

Closing this as PR#11 was merged


DeleteAsync thrown System.TypeLoadException exception

Description
DeleteAsync thrown System.TypeLoadException exception.
Exception
System.TypeLoadException : Could not load type 'Microsoft.EntityFrameworkCore.Query.RelationalQueryContextFactory' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
at Z.EntityFramework.Plus.InternalExtensions.GetDbContext[T](IQueryable1 source)    at Z.EntityFramework.Plus.BatchDelete.Execute[T](IQueryable1 query)
at Z.EntityFramework.Plus.BatchDeleteExtensions.Delete[T](IQueryable1 query, Action1 batchDeleteBuilder)
at Z.EntityFramework.Plus.BatchDeleteExtensions.<>c__DisplayClass3_01.<DeleteAsync>b__0()    at System.Threading.Tasks.Task1.InnerInvoke()
at System.Threading.Tasks.Task.<>c.<.cctor>b__274_0(Object obj)
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location where exception was thrown ---
Exception message:
System.TypeLoadException : Could not load type 'Microsoft.EntityFrameworkCore.Query.RelationalQueryContextFactory' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
Stack trace:

Further technical details

EF version: 3.1.2
EF Plus version:
Database Provider: SQLServer

Hello @Jon,
Do you think you could provide a project sample with this issue?
It will help my developer investigate the issue more efficiently.
We updated on our side the version to 3.1.2 in our unit test and we don't get any error.
We now always ask for a project sample even if the issue is easy to reproduce. As a free product, we must find some way to save time to offer an overall better experience for everyone and release fixes faster.
You can send it to<EMAIL_ADDRESS>if you need to keep the source private
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function


publish on npm

Hello!
Is your project already on npm? It'd much easier to get started with this if it was :)

No but it is planned, I have before to refactor all the code since it was my first vuejs project and it is a little bit messy...


QueryBuilder left join the same table twice bug

Hi! thanks a bunch for this awesome ORM!
Describe the bug
I'm trying to join the same table twice (this is a simplified example)
const qb = await this.patternRepository
      .createQueryBuilder('patterns')
      .select(['patterns.id', 'user.id', 'user2.id'])
      .leftJoin('patterns.user', 'user')
      .leftJoin('patterns.user', 'user2')
      .getResultList();

and getting an error
invalid reference to FROM-clause entry for table "user"
this is the resulted sql query, seems like one left join is missing
select "patterns"."id", "user"."id", "user2"."id" from "pattern" as "patterns" left join "user" as "user2" on "patterns"."userId" = "user2"."id"
Expected behavior
No error
Versions

Dependency
Version

node
14

typescript
4.1.3

mikro-orm
5

your-driver
postgresql

I don't know if it's relted, but I get an issue because of a table joined twice.
Basically, I have this structure (pseudo language, simplified for the example):
entity SeekerProfile {
  // ...
  mobilities: Collection(SeekerProfileMobility)
}

entity SeekerProfileMobility {
  // ...
  address: SeekerProfileAddress
  radius: int
}

entity SeekerProfileAddress {
  // ...
  lat: float
  lng: float
}

I would like to find all seeker profiles matching the location (the given coords should be inside their radius).
I'm trying something like:
// wrapper to .find({ filters }, [populate])
await this.seekerProfileService.load(
  {
    mobilities: {
      [expr(
        `(point(lng, lat) <@> point(${coords.lng}, ${coords.lat})) * 1.609344`,
      )]: {
        $gte: em.raw('seeker_profile_mobility.radius_internal'), // error here
      },
    },
  },
['mobilities.address'], // populate
);

This is the error I get, after running the SQL generated. How can I target my table seeker_profile_mobility without hard-code its generated alias?


arkmanager supports this as of xxxxxxx

I see alot of "arkmanager supports this as of" but when I do arkmanager upgrade nothing happens. I'm new to Github and how it work so I'm a little confused right now
my arkmanager is 1.2

The support for those things is in 1.3-dev, which we are looking at stabilizing.

Is there any ETA on when 1.3 will be replacing 1.2 ?
Le 7 août 2015 2:02 PM, "Ben Peddell"<EMAIL_ADDRESS>a écrit :

The support for those things is in 1.3-dev, which we are looking at
stabilizing.
—
Reply to this email directly or view it on GitHub
https://github.com/FezVrasta/ark-server-tools/issues/145#issuecomment-128683511
.


Adds AAAA record handling for the embedded DNS

Name to IPv6 is maintained in a separate hash table to keep the v4 lookup optimal.
Signed-off-by: Santhosh Manohar<EMAIL_ADDRESS>

@mavenugo @aboch rebased. PTAL. Multiple-A records will be returned for AAAA as well.
I will make the change on top of this to filter the AAAA queries for internal names getting forwarded to external servers.

Thanks @sanimej.
LGTM