CentOS 7: incorrect detection of public server IP

The installer suggests the following:

IPv4 or IPv6 public address: <IP_ADDRESS> peer <IP_ADDRESS>

For a newbie like me, this may appear correct (partially includes the public IP), but includes extraneous "peer <IP_ADDRESS>" which gives problems later on!
ip -4 addr output:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    inet <IP_ADDRESS> peer <IP_ADDRESS>/32 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global eth0
       valid_lft forever preferred_lft forever

In the outputs above, I obfuscated the real public IP with <IP_ADDRESS>, for obvious reasons.

Moreover it gets public IP as IP address from ethernet interface, but server can be behind NAT already then its eth0 IP4 address is <IP_ADDRESS> or sort of.
I guess that more reliable way to get it by asking some public service like we have here :
grep -m 1 -oE '^[0-9]{1,3}(\.[0-9]{1,3}){3}$' <<< "$(wget -T 10 -t 1 -4qO- "http://ip1.dynupdate.no-ip.com/" || curl -m 10 -4Ls "http://ip1.dynupdate.no-ip.com/")"

curl is most universally available. I think no need for wget at all. Just curl ifconfig.me does it for me.

I don't insist with wget. Yes curl ifconfig.me works for me too.

Closing as CentOS 7 won't be supported any more


Fix count in flake8 config

Should fix #1951

Name of the branch is not prefixed with future3, so the CI doesn't pick it up :/


Fix path for saving/retrieving toonix avatar images

Fix bug with saving/retrieving toonix avatar images (when the application is deployed) by changing the path of the folder where they are stored.

How to run it?
please i really want to play this game

How to run it?
please i really want to play this game

Hi.
OpenToonix is not playable at the moment. Only register and login are working (with some changes from the original client).
Although, if you still want to set up the server, check out the README.md file.


add openning keynote - misses meetuplink

meetupLink missing, i do not have the rights to add it to meetup... so please update once done.

meetup link added

I'm on it.


Export doesn't support the “Exclude from BOM” and “Exclude from position files” options

Please support the above-mentioned options so the BOM will not be populated with unneeded components. You can check the JLC repository for a solution: https://github.com/bennymeg/JLC-Plugin-for-KiCad/blob/master/plugins/process.py
 if not footprint.GetAttributes() & pcbnew.FP_EXCLUDE_FROM_POS_FILES:

 if not footprint.GetAttributes() & pcbnew.FP_EXCLUDE_FROM_BOM:

Valid point! Just solved it in https://github.com/AislerHQ/PushForKiCad/commit/9f3361b1aaff9d1d2f71de553698ce58cd463fe4 We will publish an updated version later today. This change still requires an update to our BOM tool which will happen later this week.


Storage Pool

Is your feature request related to a problem? Please describe.
The Container creation will fail silently if you select the wrong storage pool.
Describe the solution you'd like
Possibility to import or create storage pools from lexic

:tada: This issue has been resolved in version 0.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Quality difference between EGE-unet and u2netp

it seems that there is a significant quality difference in the output of EGE-unet and u2netp.,even in your test example. If it is in dark night sky, EGE-unet is completely unusable. If that is what expected, I think user may want to be noted in the README. Thanks.
u2netp:

EGE-unet:

EGE-unet

EGE-Unet is designed as a lightweight network, with advantages in model size, memory usage, and inference time. However, its accuracy is much lower compared to u2netp

I see. Perhaps it would be good to mention it as users may expect similar quality as direct comparison is made in README and then it could be mistaken EGE-unet to be the quality of your project.


add germanet capabilities to VFT

detect Similarities and/or Jumps between different genus and/or habitat localities

ml1:/mnt/md0/data/GermaNet/GN_V160

For using germanet on device, the database has to be converted from Postgres to sqlite

only synonyms generated from the germanet using python are used for the symbols.
Also all animal names are generated and used from germanet

done in https://github.com/th-nuernberg/memtest/issues/248


DATALOSS: switching priorities scheduler on/off loses cards that are in filtered decks.

Make a filtered deck that takes cards out of the IR deck.
Switch priorities mode on or off, which changes the note type of the IR cards.

The cards that were in the filtered deck are just lost.

When I try to replicate this, the cards are removed from the filtered deck, but they remain in the collection. Is that what you mean?

I've tried this in a few different ways. When I switch priorities mode on or off, the filtered cards return to their home deck.

If you manage to replicate this with an up-to-date install with other add-ons disabled, let me know the steps and I'll take another look at it.


RT-DETR量化后的模型是否可以转成tensorrt的模型格式

转换的命令行如下：
trtexec --onnx=rtdetr_hgnetv2_l_6x_coco_quant_dynamic.onnx --saveEngine=rtdetr_hgnetv2_l_6x_coco_quant_dynamic.engine --minShapes=images:1x3x640x640 --optShapes=images:16x3x640x640 --maxShapes=images:32x3x640x640 --shapes=images:16x3x640x640 --workspace=1024  --buildOnly
报错如下：
[06/21/2024-17:30:57] [E] Error[3]: p2o.DequantizeLinear.1357: only activation types allowed as input to this layer.
[06/21/2024-17:30:57] [E] [TRT] ModelImporter.cpp:771: While parsing node number 3294 [DequantizeLinear -> "p2o.DequantizeLinear.1358"]:
[06/21/2024-17:30:57] [E] [TRT] ModelImporter.cpp:772: --- Begin node ---
[06/21/2024-17:30:57] [E] [TRT] ModelImporter.cpp:773: input: "conv2d_0.w_0.merged.bias"
input: "p2o.helper.constant.6000"
input: "p2o.helper.constant.6001"
output: "p2o.DequantizeLinear.1358"
name: "p2o.DequantizeLinear.1357"
op_type: "DequantizeLinear"
attribute {
name: "axis"
i: 0
type: INT
}
[06/21/2024-17:30:57] [E] [TRT] ModelImporter.cpp:774: --- End node ---
[06/21/2024-17:30:57] [E] [TRT] ModelImporter.cpp:777: ERROR: ModelImporter.cpp:195 In function parseGraph:
[6] Invalid Node - p2o.DequantizeLinear.1357
p2o.DequantizeLinear.1357: only activation types allowed as input to this layer.
[06/21/2024-17:30:57] [E] Failed to parse onnx file
[06/21/2024-17:30:57] [I] Finished parsing network model. Parse time: 0.257596
[06/21/2024-17:30:57] [E] Parsing model failed
[06/21/2024-17:30:57] [E] Failed to create engine from model or file.
[06/21/2024-17:30:57] [E] Engine set up failed
请问RT-DETR量化后的模型是否可以转成tensorrt的模型格式，比如engine或者trt

训练好的模型离线量化没问题；


Service oneshot hooks might not get executed if the initial service deploy fails

The way that oneshot: true service hooks are currently implemented, they are only included in the service pod sent to the agent as part of the initial deploy_rev for the service instance. If that service pod fails to get deployed to the agent for any reason (websocket connection issues, image pull failed, etc), then the next service pod sent to the agent may not include the oneshot hooks anymore.
This behavior isn't entirely deterministic. The initial service pod  with the oneshot hooks gets cached for the initial deploy_rev by both the server and the agent, so it is possible for the agent to retry the apply for the container with the initial service pod config, and in that case, the oneshot hook would get executed. However, that doesn't happen if the cache gets invalidated for any reason (the server LRU cache entry gets evicted, the service is re-deployed by the server to a different node where the agent is connected to a different server worker, or the agent reconnects to a different server worker).
Example with a broken image that gets fixed with a re-deploy
stack: test/hooks-oneshot
services:
  redis:
    image: redis:nonexist
    hooks:
      post_start:
        - name: test-oneshot
          cmd: echo "post-start oneshot hook"
          instances: '*'
          oneshot: true
        - name: test-2
          cmd: echo "post-start hook 2"
          instances: '*'

$ bin/kontena stack install test/hooks-oneshot.yaml
 [done] Creating stack hooks-oneshot
 [done] Triggering deployment of stack hooks-oneshot
 [done] Waiting for deployment to start
 [fail] Deploying service redis
Deployment of service development/hooks-oneshot/redis failed:
  - halting deploy of development/hooks-oneshot/redis, one or more instances failed
  - GridServiceInstanceDeployer::ServiceError: Docker::Error::NotFoundError: No such image: redis:nonexist (on node core-01)
$ bin/kontena stack upgrade hooks-oneshot test/hooks-oneshot.yaml
 [done] Parsing test/hooks-oneshot.yaml
 [done] Reading stack hooks-oneshot from master
 [done] Upgrading stack hooks-oneshot
 [done] Triggering deployment of stack hooks-oneshot
 [done] Waiting for deployment to start
 [done] Deploying service redis
$ bin/kontena stack logs -f hooks-oneshot
2017-09-20T11:07:54.000Z [hooks-oneshot.redis-1]: running post_start hook: echo "post-start hook 2"
2017-09-20T11:07:55.000Z [hooks-oneshot.redis-1]: post-start hook 2
2017-09-20T11:07:56.000Z [hooks-oneshot.redis-1]: 1:C 20 Sep 11:07:56.181 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
2017-09-20T11:07:56.000Z [hooks-oneshot.redis-1]: 1:C 20 Sep 11:07:56.182 # Redis version=4.0.1, bits=64, commit=00000000, modified=0, pid=1, just started

Note the non-oneshot hook getting executed without the oneshot hook being executed.

Fixed in #2701 because the oneshot hook marking happens much later during the deploy, after the image pull and network-ready wait. In particular, for post_start hooks, the oneshot hooks are only marked for execution after the service container has actually been created and started.
The oneshot hooks might still not get executed if the oneshot hook marking fails, or if the hook exec itself somehow fails (e.g. the container dies).
There is also no way to retry hooks that exit with an error code, and any remaining hooks will not get executed either... hook exec retry on hook errors is probably a separate issue.


evm/db: Drop _to_db suffix of ChainDB's persist* methods

Also refactor ChainDB.persist_block() to create a new method that
persist only uncles -- needed by ChainSyncer

ping @carver this is going to cause breakage in eth-tester.  We should be sure the py-evm backend is pinned to a specific version before making a new py-evm release with these changes.

We should be sure the py-evm backend is pinned to a specific version before making a new py-evm release with these changes.

@pipermerriam argh, it used to be, for just that reason, but it got undone. Thanks for the heads-up.

Option 1 - Start to establish stable APIs in py-evm, and accept the overhead of a deprecation process.
Option 2 - Status-Quo, pin to exact alpha versions and deal with the issues as they arise.

I am in favor of 2 because we're still figuring things out in certain places in py-evm and these changes should become less and less frequent.

Yes, totally agree on option 2. Depending on an alpha means accepting API risk, which also means the safest thing to do is pin to a specific version :+1:


#39 Extended support for wildcard types to use the upper bound

Extended support for wildcard types to use the upper bound if no other type information is available and the type has only a single upper bound. Otherwise, it defaults to the same Object type.

Coverage increased (+0.42%) to 84.31% when pulling ea76bf3c2381d3881b75e6c97223670fde769ddc on feature/Pop-39-generic-runtime-wildcard-support into 53cd4ddf9c516bbd36b30c596f05b52edc4675ff on master.


[AMHACK] [Query] Permission tree contains plenty of permission lists - Do we have a use of those permissions?

Description:
As $subject I can see lists of permissions in permission tree at admin console. As I refered the doc in [1] I understood the role based permissions. There basically 4 roles was explained and limited number of permissions was assigned to those roles even.
Do we have use of other permissions? If so do we have any doc reference to understand what are those? (As I searched I couldn't find any other doc)
e.g.

[1] [https://docs.wso2.com/display/AM210/Adding+User+Roles]
Suggested Labels:
2.1.0
Suggested Assignees:

Affected Product Version:
APIM-2.1.0
OS, DB, other environment details and versions:
Steps to reproduce:

answered.


Update microsoft-defender-endpoint-mac.md remove Big Sur as supported version

If the three most recent major releases are the only one supported then the listing to Big Sur needs removed.

@YongRhee-MSFT , can you confirm this change? If so, I will merge. Thx!

Hi Dan,
Thx for following up.
Confirming, Apple dropped support for BigSur at the end of Nov '23.
@.***
Thx,
Yong
From: Daniel Simpson @.>
Sent: Friday, February 16, 2024 11:26 AM
To: MicrosoftDocs/microsoft-365-docs @.>
Cc: Yong Rhee @.>; Mention @.>
Subject: Re: [MicrosoftDocs/microsoft-365-docs] Update microsoft-defender-endpoint-mac.md remove Big Sur as supported version (PR #13382)
@YongRhee-MSFThttps://github.com/YongRhee-MSFT , can you confirm this change? If so, I will merge. Thx!

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/microsoft-365-docs/pull/13382#issuecomment-1949193894, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANN7NO5OTJVUKIRXT7WOOHDYT6XEDAVCNFSM6AAAAABDGVH2ZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZGE4TGOBZGQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Break into Modules [WIP]

Fixes #38

Hi! Thanks for PR.
Make sure you have checked points in PR Template correctly.
(Powered by GitMate.io)


Failed to create Container Apps Environment with custom virtual network

Please provide us with the following information:

This issue is a: (mark with an x)

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
In West Europe region I have failed to create Container Apps Environment with virtual network. I followed documentation provided here.
Tried both with Azure CLI and Azure Powershell.
Steps to reproduce

Copy paste all commands from documentation until New-AzContainerAppManagedEnv (including it) into powershell script.
Run script.

Expected behavior
Successfully create Container Apps Environment with connection to subnet
Actual behavior
Error message is display:
Message: Fail to create managed environment because provided subnet Id is invalid
Screenshots

Additional context
The issue occurred when using Azure Portal, Azure CLI and Azure Powershell.
Additionally I paste my powershell script:
$LOCATION='west europe'
$SubnetArgs = @{
    Name = $SUBNET_NAME
    AddressPrefix = '<IP_ADDRESS>/23'
}
$subnet = New-AzVirtualNetworkSubnetConfig @SubnetArgs

$VnetArgs = @{
    Name = $VNET_NAME
    Location = $LOCATION
    ResourceGroupName = $RESOURCE_GROUP
    AddressPrefix = '<IP_ADDRESS>/16'
    Subnet = $subnet
}
$vnet = New-AzVirtualNetwork @VnetArgs
$InfrastructureSubnet=(Get-AzVirtualNetworkSubnetConfig -Name $SubnetArgs.Name -VirtualNetwork $vnet).id

$WorkspaceArgs = @{
    Name = 'myworkspace'
    ResourceGroupName = $RESOURCE_GROUP
    Location = $LOCATION
    PublicNetworkAccessForIngestion = 'Enabled'
    PublicNetworkAccessForQuery = 'Enabled'
}
New-AzOperationalInsightsWorkspace @WorkspaceArgs
$WorkspaceId = (Get-AzOperationalInsightsWorkspace -ResourceGroupName $RESOURCE_GROUP -Name $WorkspaceArgs.Name).CustomerId
$WorkspaceSharedKey = (Get-AzOperationalInsightsWorkspaceSharedKey -ResourceGroupName $RESOURCE_GROUP -Name $WorkspaceArgs.Name).PrimarySharedKey

$EnvArgs = @{
    EnvName = $CONTAINERAPPS_ENVIRONMENT
    ResourceGroupName = $RESOURCE_GROUP
    Location = $LOCATION
    AppLogConfigurationDestination = 'log-analytics'
    LogAnalyticConfigurationCustomerId = $WorkspaceId
    LogAnalyticConfigurationSharedKey = $WorkspaceSharedKey
    VnetConfigurationInfrastructureSubnetId = $InfrastructureSubnet
    VnetConfigurationInternal = $true
}
New-AzContainerAppManagedEnv @EnvArgs

I had the same issue using Pulumi. I kinda solved it in a way that I created the Container App Environment in Azure Portal, then deleted it and re-created using Pulumi. I believe creating the environment for the first time via Azure Portal enables something, that's why subsequent deployments work correctly from Pulumi. Hope that helps :)

I run into the same the same issue (after registering both providers) @kendallroden , via Azure CLI
"azure-cli": "2.39.0",
  "extensions": {
    "containerapp": "0.3.13",

provide argument pointing to VNET subnet: --infrastructure-subnet-resource-id /subscriptions/36470000-0000-0000-0000-000000000000/resourceGroups/*****-poc/providers/Microsoft.Network/virtualNetworks/*****poc-vnet/subnets/container-environment. Thinking the default NSG (rules without explicit NSG) might be interfering, created a NSG following these instructions: https://learn.microsoft.com/en-us/azure/container-apps/firewall-integration. Errors remains.

Retried after configuring subnet delegation with Microsoft.Apps/environments, but wasn't a solution :)

I tried to create it through portal like @macpak suggested and environment created successfully, but it is without having --internal-only flag set. Will try to recreate it through CLI when I find a minute.
I'm not sure about Microsoft.OperationalInsights, but I had Microsoft.ContainerService registered for sure. Right now both are registered.

Are you still seeing this issue @pbakun

I am seeing this issue when I try to create an app env with the CLI

az containerapp env create `
    -n c2c-appenvironment `
    -l centralus `
    -g c2c-shared `
    --logs-workspace-id $WORKSPACE_ID `
    --logs-workspace-key $workspaceKey `
    -s $INFRASTRUCTURE_SUBNET `
    -z

{
"azure-cli": "2.42.0",
"azure-cli-core": "2.42.0",
"azure-cli-telemetry": "1.0.8",
"extensions": {
"application-insights": "0.1.16",
"azure-devops": "0.25.0",
"containerapp": "0.3.13",
"cosmosdb-preview": "0.21.0",
"front-door": "1.0.17",
"interactive": "0.4.5",
"mesh": "0.10.7",
"storage-preview": "0.8.3"
}
}

Closing an issue only because time passed-by? Would be nice if all issues disappear by just sitting out :)
@kendallroden why the question, was there a CLI update with potential fix, or backend update on the resourceprovider perhaps?
https://github.com/microsoft/azure-container-apps/issues/451#issuecomment-1299326294

I am encountering this as well with bicep.  We were still specifying both subnets (infrastructureSubnetId and runtimeSubnetId).  runtimeSubnetId property is deprecated according to this:
https://github.com/microsoft/azure-container-apps/issues/374
Hoping this resolves our issue.  I will report back if it does and I remember to do so.

Removing runtimeSubnetId from the bicep definition did appear to fix our issue, but we've seen quite a bit of intermittency with Azure Container App environment creation so it's difficult to say with certainty that was the fix.  I believe it was.

The issue is closed automatically when the poster is requested to provide info and doesn't respond within a given period of time! Will keep it open if this is still an issue @markdebruijne

Hi @hoffmanntravis I am glad you were able to remove the runtimeSubnetId and resolve your issue. Wondering if you are still running into this or if it is potentially just intermittent? Trying to get reproducible failure. @markdebruijne

Hi, sorry for beeing so quiet, but I recently had a lot on my head.
I just tried to create containerapp environment with vnet again on new subscription after using az containerapp env show I got:
"deploymentErrors": "ErrorCode: ManagedEnvironmentSubnetIdInvalid, Message: Fail to create managed environment because provided subnet Id is invalid, refer to
https://go.microsoft.com/fwlink/?linkid=2198255 for more detail.",
"provisioningState": "Failed",

So it seems that the issue is still there. I guess the workaround with creating it couple times through Azure Portal will finally make it work like last time, but I don't think this should be a way to go with it.

@kendallroden  Hi Kendall.  Unfortunately it looks like this popped up in a fresh deploy for us via bicep tonight for a new client (so all new resources, new resource group, etc) without the runtimeSubnetId property set from the start.  I am able to see the deployment status in the json view of the container environment so we notice before an hour and cancel the deploy, but it usually takes me 15 minutes to realize something went south.
The more difficult part is so far the fix seems to be to keep deleting the resource and re-deploying until it works.  It's possible there is some sort of race condition in our bicep but I'm not sure what it would be or how.  We explored that pretty carefully.  Honestly it feels more like a backend timing issue but that's a bit of a guess.

One thing I have noticed is it seems like container environment creation is only available in the UI if I first try to create a container app and then create the container environment as a new resource inside a sub menu.  Is it valid to create a container environment without any containers referenced either in bicep or through other tooling?  We are dynamically creating containers based on some information in bicep via a module with a loop and a batch size of 1.  I'm wondering if that might be related here somehow to this?  Perhaps it has nothing to do with anything.
@batchSize(1)
module containers 'resources-container.bicep' = [for item in buildInfo.Containers: {
  name: item.name

relevant lines of code ^.  buildInfo.Containers is a deserialized JSON list of objects.

I have encountered this issue myself. While trying to identify the root issue, I have created the minimal example below to reproduce the issue. It results in the following non-descript error:
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The deployment operation status is unknown."
    }
}

but annoyingly, the status on Azure shows the deployment as still "In progress" (or in the CLI, it shows as "Running ...")

Minimal Bicep Example
param location string = resourceGroup().location

resource vnet 'Microsoft.Network/virtualNetworks@2022-01-01' = {
  name: 'vnet-${uniqueString(resourceGroup().id)}'
  location: location

  properties: {
    addressSpace: {
      addressPrefixes: [ '<IP_ADDRESS>/16' ]
    }

    subnets: [
      {
        name: 'default'
        properties: {
          addressPrefix: '<IP_ADDRESS>/24'
        }
      }
      {
        name: 'cae'
        properties: {
          addressPrefix: '<IP_ADDRESS>/23'
          delegations: [
            {
              name: 'ContainerAppEnvironmentDelegation'
              properties: {
                serviceName: 'Microsoft.App/environments'
              }
            }
          ]
        }
      }
    ]
  }

  resource defaultSubnet 'subnets' existing = {
    name: 'default'
  }
  resource caeSubnet 'subnets' existing = {
    name: 'cae'
  }
}

resource managementEnvironment 'Microsoft.App/managedEnvironments@2022-06-01-preview' = {
  name: 'cae-${uniqueString(resourceGroup().id)}'
  location: location
  sku: {
    name: 'Consumption'
  }

  properties: {
    vnetConfiguration: {
      internal: true
      infrastructureSubnetId: vnet::caeSubnet.id
    }
  }
}

In the example above, it does not seem to matter whether internal: true or internal: false matters. If I comment out vnetConfiguration is commented out, the deployment succeeds.

This is the error that appears when executing infinitely by the way when you look in resource group deployments for the container environment.  I didn't have a sample the other day, but I do today.
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The deployment operation status is unknown."
    }
}

I did see this error in this latest deploy.  Not sure if this is related root cause or not, but we are referencing the insights like this in bicep:
resource containerEnv 'Microsoft.App/managedEnvironments@2022-01-01-preview' = {
  name: buildInfo.Resources.ContainerAppEnvironment.name
  location: buildInfo.Resources.ContainerAppEnvironment.location
  tags: buildInfo.Tags
  properties: {
    appLogsConfiguration: {
      destination: 'log-analytics'
      logAnalyticsConfiguration: {
        customerId: logAnalytics.properties.customerId
        sharedKey: logAnalytics.listKeys().primarySharedKey
      }
    }
    vnetConfiguration: {
      internal: true
      infrastructureSubnetId: ctrlSubnetId
    }
  }
}

The Resource 'Microsoft.Insights/components/' under resource group '' was not found

I attempted to create manually in the portal after having a failed deployment via create the resource in a failed state and got the error below (I did that by mistake, but it might be a useful data point):
"deploymentErrors": "ErrorCode: ManagedEnvironmentUpgradeError, Message: Update the managed environment failed."
Also, relative to my previous point logAnalytics dependsOn appears superfluous if I add it manually to bicep, but Microsoft.OperationalInsights/workspaces still might be some sort of dependency or race condition etc.

I just noticed @JP-Ellis-KPMG and myself are on preview versions of bicep... :disappointed: will be testing this against general availability Microsoft.App/managedEnvironments@2022-03-01 to see if that improves things

We have had two good fresh deploys without any issues using the GA sku over the preview sku in bicep.  Not sure that is enough data to say that was the cause for certain, but wanted to share that detail.  Previously we were seeing many failures and had not seen clean executions across at least 10 new environment buildouts until we switched skus.

For creation failed with invalid subnet Id, several comments,

Make sure you have run "az provider register -n Microsoft.ContainerService" if you are using cli/arm template/bicep
Make sure the subnet is not delegated any service. Azure container apps subnet does require delegation yet.

If you still see issues, let us know.

This is an issue for us, we are unable to deploy container apps from the Azure Portal.

We are trying to deploy from the Azure portal and selecting our own VNet. The deployment status stalls with
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The deployment operation status is unknown."
    }
}

For creation failed with invalid subnet Id, several comments,

Make sure you have run "az provider register -n Microsoft.ContainerService" if you are using cli/arm template/bicep
Make sure the subnet is not delegated any service. Azure container apps subnet does require delegation yet.

If you still see issues, let us know.

@chinadragon0515 not sure what you're saying regarding 2): Azure container apps subnet does require delegation yet? Or did you mean to say: Azure container apps subnet does not require delegation yet?

I believe this issue is still ongoing. I was trying to deploy via the portal and it was timing out with no proper error message. I tried multiple things and finally got to make it work. The primary issue that I found is undocumented.
In the azure document, it is written that any subnet equal to or larger than /23 will work, however, this was not the case. I tried a deployment with /21 subnet in VNET and it didn't fail. I believe this is the solution to the entire issue.
Make sure you have the required providers registered. And after deployment, you will also be needing a private DNS zone to make private endpoints resolvable from other resources.

We are trying to deploy from the Azure portal and selecting our own VNet. The deployment status stalls with
{
    "status": "Failed",
    "error": {
        "code": "ResourceDeploymentFailure",
        "message": "The deployment operation status is unknown."
    }
}

We are practically unable to deploy our service.

Checkout my above comment. This may fix your issue.

Can anyone confirm if you need a /21 subnet for zone redundancy?
For us a /23 subnet failes when adding zone redundancy, while it succeeds without zone redundancy.

I'm still facing this issue either using Azure Portal or Azure Powershell. The environment creation takes 30 mins and eventually fails. The error message I got in Portal was:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"OperationFailed","message":"Managed environment failed to initialize due to managed cluster provision failed"}]}

I'm having the same issue - I've tried increasing the subnet to /21 and that made no difference I've also tried deploying via bicep and in the portal
In the bicep example I created the vnet and subnet in advance and in the portal I used the wizard to create a new vnet and subnet (but used an existing log workspace) and it failed after 6-7 minutes with the same error
"Managed environment failed to initialize due to cluster provision failed"
I was able to create the container app environment without the vnet integration in both portal and bicep with no issues

An update - I was able to resolve the deployment failure so posting here in case it helps
After reading this comment I checked to see whether this could be the cause of my issue - it seems that for vnet integration the service creates an additional resource group and resources with the resource group name starting with MC_
Our subscription had some policy constraints that enforced certain tags to be present when creating a new resource group and sure enough these had triggered events during my container app deployments
When the policy was disabled I was able to create the vnet integrated container app without issue

An update - I was able to resolve the deployment failure so posting here in case it helps After reading this comment I checked to see whether this could be the cause of my issue - it seems that for vnet integration the service creates an additional resource group and resources with the resource group name starting with MC_ Our subscription had some policy constraints that enforced certain tags to be present when creating a new resource group and sure enough these had triggered events during my container app deployments When the policy was disabled I was able to create the vnet integrated container app without issue

Can anyone confirm that this is the case? Its very common to have these restrictions on an enterprise environment and if we need to make policy exemptions this should be outlined in the documentation.

It would be great if the Container Apps Team would post a bicep example demonstrating the successful provisioning of an internal Container Environment with subnet.

Same issue on our subscription. I can create a Container Apps environment on an existing vnet with 2 subnets on the Portal, one default, which is not offered by the UI and a second which is made /23, but when I try to create the same environment from the Azure CLI I get:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
No details given on the event log.
I can't really recommend using ContainerApps at the moment for any solution without proper provisioning commands we can use.
If anything, the fix to this problem should be adding details to the errors raised, which are probably a set of multiple issues.

So do I have got the same issue. I had to create a brand-new environment and a Container App on Azure portal firstly, then it was succeeded to create with the other command I would like to use like: az containerapp compose create (by default this command doesn't have an argument to create new environment and apps with a VNET).

Same issue on our subscription. I can create a Container Apps environment on an existing vnet with 2 subnets on the Portal, one default, which is not offered by the UI and a second which is made /23, but when I try to create the same environment from the Azure CLI I get:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
No details given on the event log.
I can't really recommend using ContainerApps at the moment for any solution without proper provisioning commands we can use.
If anything, the fix to this problem should be adding details to the errors raised, which are probably a set of multiple issues.

Same issue here, unable to create a containerapp environment using Azure CLI (latest version 2.60.0) using --infrastructure-subnet-resource-id, I get the following error:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
The resource exists and the resource ID that is being used is valid (verified in Azure Resource Explorer).

Same issue on our subscription. I can create a Container Apps environment on an existing vnet with 2 subnets on the Portal, one default, which is not offered by the UI and a second which is made /23, but when I try to create the same environment from the Azure CLI I get:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
No details given on the event log.
I can't really recommend using ContainerApps at the moment for any solution without proper provisioning commands we can use.
If anything, the fix to this problem should be adding details to the errors raised, which are probably a set of multiple issues.

Same issue here, unable to create a containerapp environment using Azure CLI (latest version 2.60.0) using --infrastructure-subnet-resource-id, I get the following error:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
The resource exists and the resource ID that is being used is valid (verified in Azure Resource Explorer).

Hi @WEMcJJJ
Can you should me the commands you create the sub-net? Thanks.
Or can you show me the delegation of the subnet with this command?:
az network vnet subnet show -g {resource-group} -n {subnet-name} --vnet-name {vnet-name}
For --infrastructure-subnet-resource-id, the subnet used should be delegated to Microsoft.App/environments：
az network vnet subnet create --address-prefixes '<IP_ADDRESS>/23' --delegations Microsoft.App/environments -n sub -g {resource_group} --vnet-name {vnet}

Same issue on our subscription. I can create a Container Apps environment on an existing vnet with 2 subnets on the Portal, one default, which is not offered by the UI and a second which is made /23, but when I try to create the same environment from the Azure CLI I get:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
No details given on the event log.
I can't really recommend using ContainerApps at the moment for any solution without proper provisioning commands we can use.
If anything, the fix to this problem should be adding details to the errors raised, which are probably a set of multiple issues.

Hi @WEMcJJJ @vienleidl
May I ask what is the location the vnet in and what is the command you used to create the containerapp environment?
The location should be consistent, need to specify the location with --location:
az containerapp env create -g {resource-group} -n {env-name} --location {vnet-location} --logs-destination none -s {subnet} --debug

Same issue on our subscription. I can create a Container Apps environment on an existing vnet with 2 subnets on the Portal, one default, which is not offered by the UI and a second which is made /23, but when I try to create the same environment from the Azure CLI I get:
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.
No details given on the event log.
I can't really recommend using ContainerApps at the moment for any solution without proper provisioning commands we can use.
If anything, the fix to this problem should be adding details to the errors raised, which are probably a set of multiple issues.

Hi @WEMcJJJ @vienleidl
May I ask what is the location the vnet in and what is the command you used to create the containerapp environment? The location should be consistent, need to specify the location with --location: az containerapp env create -g {resource-group} -n {env-name} --location {vnet-location} -s {subnet} --debug

The issue is with --infrastructure-subnet-resource-id taking a subnet id looking like a filesystem path. That I fixed with:
MSYS2_ARG_CONV_EXCL="*" az containerapp env create --name "$CONTAINER_ENV" --resource-group "$RESOURCE_GROUP_NAME"...

@Greedygre - I followed the Microsoft tutorial here. I modified the variables a little to fit in with work I was already doing. Location was the same for all resources created (westus2).
az network vnet create \
  --resource-group $RESOURCE_GROUP \
  --name $VNET_NAME \
  --location $LOCATION \
  --address-prefix <IP_ADDRESS>/16
  --tags $TAGS

az network vnet subnet create \
  --resource-group $RESOURCE_GROUP \
  --vnet-name $VNET_NAME \
  --name $SUBNET_NAME \
  --address-prefixes <IP_ADDRESS>/23

Here's what I used to try to create the environment:
INFRASTRUCTURE_SUBNET=$(az network vnet subnet show --resource-group ${RESOURCE_GROUP} --vnet-name $VNET_NAME --name $SUBNET_NAME --query "id" -o tsv)

az containerapp env create \
  --name $CONTAINER_ENVIRONMENT \
  --resource-group $RESOURCE_GROUP \
  --location $LOCATION \
  --infrastructure-subnet-resource-id $INFRASTRUCTURE_SUBNET \

As far as the delegation is concerned, I ran the following command:
az network vnet subnet show -g $RESOURCE_GROUP -n $SUBNET_NAME --vnet-name $VNET_NAME
And there were no delegations listed:
{
  "addressPrefix": "<IP_ADDRESS>/23",
  "delegations": [],

I got the same result if I ran the following:
 az network vnet subnet show \
    --resource-group $RESOURCE_GROUP \
    --name $SUBNET_NAME \
    --vnet-name $VNET_NAME\
    --query delegations
[]

I tried your suggestion to add the --delegations options (with and without quotes), when creating the subnet, but either way it said "--delegations: command not found".
az network vnet subnet create \
  --resource-group $RESOURCE_GROUP \
  --vnet-name $VNET_NAME \
  --name $SUBNET_NAME \
  --address-prefixes <IP_ADDRESS>/23
  --delegations "Microsoft.App/environments"

I did some more digging and tried some suggestions here, and the following worked (not sure why it wouldn't work with the create command):
az network vnet subnet update \
    --resource-group $RESOURCE_GROUP \
    --name $SUBNET_NAME \
    --vnet-name $VNET_NAME\
    --delegations Microsoft.App/environments

After running the above, it now shows the delegation if I query it:
az network vnet subnet update \
    --resource-group $RESOURCE_GROUP \
    --name $SUBNET_NAME \
    --vnet-name $VNET_NAME\
    --query delegations
[
  {
    "actions": [
      "Microsoft.Network/virtualNetworks/subnets/join/action"
    ],
    "etag": "W/\"xxxxx-xxxxx-xxxxx-xxxxx\"",
    "id": "/subscriptions/xxxxx-xxxxx-xxxxx-xxxxx/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vnetName>/subnets/infrastructure-subnet/delegations/0",
    "name": "0",
    "provisioningState": "Succeeded",
    "resourceGroup": "<rgName>",
    "serviceName": "Microsoft.App/environments",
    "type": "Microsoft.Network/virtualNetworks/subnets/delegations"
  }
]

However, I am still not able to create the environment:
az containerapp env create \
  --name $CONTAINER_ENVIRONMENT \
  --resource-group $RESOURCE_GROUP \
  --location $LOCATION \
  --infrastructure-subnet-resource-id $INFRASTRUCTURE_SUBNET

No Log Analytics workspace provided.
Generating a Log Analytics workspace with name "workspace-<rgName>"
(ManagedEnvironmentInvalidNetworkConfiguration) The environment network configuration is invalid: Invalid vnet resource ID provided, or the virtual network could not be found.

I verified that the resource ID appears to be correct:
echo $INFRASTRUCTURE_SUBNET
/subscriptions/xxxxx-xxxxx-xxxxx-xxxxx/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vNetName>/subnets/infrastructure-subnet

As previously stated, I'm running the latest version of Azure CLI:
az version
{
  "azure-cli": "2.60.0",
  "azure-cli-core": "2.60.0",
  "azure-cli-telemetry": "1.1.0",
  "extensions": {}
}

Just to double-check, I ran the exact same command to create the environment in Azure Cloud Shell, and it worked...go figure. Not sure why it works in Azure Cloud Shell and not locally.
@gpwink - not sure I follow, I tried running the following and still get the same error (even tried putting each variable in double quotes (i.e. "$INFRASTRUCTURE_SUBNET"):
MSYS2_ARG_CONV_EXCL="*" az containerapp env create \
  --name $CONTAINER_ENVIRONMENT \
  --resource-group $RESOURCE_GROUP \
  --location $LOCATION \
  --infrastructure-subnet-resource-id $INFRASTRUCTURE_SUBNET \

I even tried manually putting in the subnet resource ID without a leading "/" and with a a double "//" at the beginning and that didn't make any difference, still got an error. .

INFRASTRUCTURE_SUBNET=$(az network vnet subnet show --resource-group ${RESOURCE_GROUP} --vnet-name $VNET_NAME --name $SUBNET_NAME --query "id" -o tsv)

Hi @WEMcJJJ
Can you execute the az containerapp env create command with --debug? I want to check the value of  --infrastructure-subnet-resource-id in the command arguments. I checked some logs and found there is some invalid string included in it when throw this error, please help to confirm, thanks! Just like this:
"infrastructureSubnetId": "C:/Program Files/Git/subscriptions/xxxxx-xxxxx-xxxxx-xxxxx/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vNetName>/subnets/infrastructure-subnet
",

I can repro it when I using Gitbash in windows. The command arguments like this:
$ az containerapp env create -g <rg> -n <env-name> --location northcentralus  --logs-destination none --infrastructure-subnet-resource-id $INFRASTRUCTURE_SUBNET  --debug
DEBUG: cli.knack.cli: Command arguments: ['containerapp', 'env', 'create', '-g', '<rg>', '-n', '<env-name>', '--location', 'northcentralus', '--logs-destination', 'none', '--infrastructure-subnet-resource-id', 'C:/Program Files/Git/subscriptions/xxxxx-xxxxx-xxxxx-xxxxx/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<vNetName>/subnets/infrastructure-subnet', '--debug']

@Greedygre - looks like that's the issue. I'm using Gitbash in Windows and the argument gets modified:
az containerapp env create \
  --name $CONTAINER_ENVIRONMENT \
  --resource-group $RESOURCE_GROUP \
  --location $LOCATION \
  --infrastructure-subnet-resource-id $INFRASTRUCTURE_SUBNET \
  --debug
cli.knack.cli: Command arguments: ['containerapp', 'env', 'create', '--name', '<envName>', '--resource-group', '<rgName>', '--location', 'westus2', '--infrastructure-subnet-resource-id', 'C:/Program Files/Git/subscriptions/<SubID>/resourceGroups/<rgName>/providers/Microsoft.Network/virtualNetworks/<VNetName>/subnets/infrastructure-subnet', '--debug']
cli.knack.cli: __init__ debug log:
Enable color in terminal.
cli.knack.cli: Event: Cli.PreExecute []

@Greedygre - looks like that's the issue. I'm using Gitbash in Windows and the argument gets modified:
@WEMcJJJ
The argument got modified by Git Bash, Git Bash will convert some paths to POSIX paths.

@Greedygre - looks like that's the issue. I'm using Gitbash in Windows and the argument gets modified:  @WEMcJJJ
The argument got modified by Git Bash, Git Bash will convert some paths to POSIX paths. You can use powershell or CMD.

What a pain. :( @Greedygre, thanks for helping me figure it out though!

As a heads up. The issue for me is related to how the Virtual network is created. You can define the virtual network with either an addressPrefix or addressPrefixes block.
If you use an address prefixes block on your VNET like this:

It appears that the container apps environment will fail validation with the following message.
 performing CreateOrUpdate: unexpected status 400 with error: ManagedEnvironmentInvalidNetworkConfiguration: The environment network configuration is invalid: The subnet and its addressPrefix could not be found.

If you recreate your VNET specifying only an addressPrefix it will pass the validation and create the container app enviroment.

100% - this question was asked in Microsoft Q&A and I came to the same conclusion; I raised a blog post: https://luke.geek.nz/azure/containerapps-env-missing-subnet/


.gitignore possible to place it in another path, via extra settings?

Wonder if this is possible somehow at this moment? We'd like to place the .gitignore created by WP Starter, in another subfolder instead of the root level from where composer is run, e.g. inside <root>/public/
Is this something currently achievable trough extra settings in the composer.json file?
In case is not, could be implemented for a future WP Starter release? Thinking about:
{
    "extra" : {
        "wpstarter" : {
            "gitignore-path" : "./public",
            "prevent-overwrite" : [
                ".gitignore"
            ],
        }
    }
}

Hi @elvismdev and thanks for your interest.
At the moment that's not possible. But more flexibility on file creation is already planned in version 3 which is in the works, but no ETA.

Wonder if this is possible somehow at this moment? We'd like to place the .gitignore created by WP Starter, in another subfolder instead of the root level from where composer is run, e.g. inside /public/

@elvismdev what's the use case for this?

For v2 this is not gonna change.
For v3 I've reconsidered the creation of a gitignore step at all, my experience in 3 years usage of WP Starter has been that manually created .gitignore has worked best.
With custom steps in v3 people can create one if they want. So this issue make no much sense to be opened.
Thanks anyone involved.


Profile pages icon links broken

Links should be page-relative anchor links, but they appear to be absolute and end up taking you to the home page instead of scrolling to the pertinent section on the current profile page.

this one is partially feed and now replaced by #25


Not able to start training. Give mel2wav not found error

Traceback (most recent call last):
File "scripts/train.py", line 1, in
from mel2wav.dataset import AudioDataset
ModuleNotFoundError: No module named 'mel2wav'

Try:  PYTHONPATH=$PWD:$PYTHONPATH python

I am trying to run the train.py file on colab using !python path and it gives me this error. What should I possible do ? The structure of that folder is

and this is how i am trying to run it on colab.

any help is highly appreciated


Hash #top in url and ignoring history updating

Hello! So my suggestions:

Possibility for "go to top" button which excluding from browser history urls like "mysite.com/#top" or "mysite.com/#" . I can realize it with initialization of two instances like (example):

var scroll = new SmoothScroll('a[href*="#"]', {
  ignore: 'a[href="#"]'
});

var scroll2 = new SmoothScroll('a[href="#"]', {
  updateURL: false
});

But possibility for ignoring history updating for custom selectors with option like: options.ignoreUpdateUrl will be helpful.

Also i see what "#top" is hardcoded name here. Possibility for customization this name with options like: options.emptyHashSelector also will be useful

Hi there, I'm deprecating this plugin and recommending everyone switch over to a now well supported CSS-native approach: https://gomakethings.com/how-to-animate-scrolling-to-anchor-links-with-one-line-of-css/


Bugfix request

I'm being threatened with murder.

Help me

You got out of the problem by pressing the star.


Maybe remove some stone types? There are too many

For now no with the urging of @TulkinRB. Might revisit this later


Azure.Core, Version=1.25 is trying to load System.Text.Json, Version=<IP_ADDRESS>

This is happening in an ASP.NET 4.8 MVC 5 app.  The same code works fine if I revert back to Azure.Core, Version=1.14
Fusion Log:
=== Pre-bind state information ===
LOG: DisplayName = System.Text.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51
(Fully-specified)
LOG: Appbase = file:///C:/Users/msherrane/Source/Workspaces/TFS/Dev/Web/ELinkMvc/ELinkMvc/
LOG: Initial PrivatePath = C:\Users\User\Source\Workspaces\TFS\Dev\Web\ELinkMvc\ELinkMvc\bin
Calling assembly : Azure.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=92742159e12e44c8.
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Users\User\Source\Workspaces\TFS\Dev\Web\ELinkMvc\ELinkMvc\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: System.Text.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/elinkmvc/55fc4c7c/d2691189/System.Text.Json.DLL.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/elinkmvc/55fc4c7c/d2691189/System.Text.Json/System.Text.Json.DLL.
LOG: Attempting download of new URL file:///C:/Users/User/Source/Workspaces/TFS/Dev/Web/ELinkMvc/ELinkMvc/bin/System.Text.Json.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Major Version
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
Stack Trace:
at Azure.Core.Pipeline.ClientDiagnostics.CreateRequestFailedExceptionAsync(Response response, ResponseError error, IDictionary2 additionalInfo, Exception innerException)    at Azure.Storage.Blobs.BlobRestClient.<GetPropertiesAsync>d__11.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Azure.Storage.Blobs.Specialized.BlobBaseClient.<GetPropertiesInternal>d__119.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Azure.Storage.Blobs.Specialized.BlobBaseClient.<ExistsInternal>d__113.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Azure.Storage.Blobs.Specialized.BlobBaseClient.<ExistsAsync>d__112.MoveNext()    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Custard.BusinessObjects.Entities.BusinessObjectBase1.<>c__DisplayClass14_0.<<DownloadBlob>b__0>d.MoveNext() in C:\Users\User\Source\Workspaces\TFS\Dev\Assemblies\BusinessObjects\Entities\BusinessObjectBase.cs:line 163    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Custard.Classes.AsyncUtil.RunSync[TResult](Func1 task) in C:\Users\User\Source\Workspaces\TFS\Dev\Assemblies\Classes\UnsecuredBusinessBase.cs:line 2614    at Custard.BusinessObjects.Entities.BusinessObjectBase1.DownloadBlob(String azureBlobPath) in C:\Users\User\Source\Workspaces\TFS\Dev\Assemblies\BusinessObjects\Entities\BusinessObjectBase.cs:line 157
at Custard.BusinessObjects.Entities.BusinessObjectBase`1.RetrieveAttachmentFromStorage(String callingMemberName) in C:\Users\User\Source\Workspaces\TFS\Dev\Assemblies\BusinessObjects\Entities\BusinessObjectBase.cs:line 253
at Custard.BusinessObjects.Entities.ClaimPhoto.get_Attachment_DatabaseOrBlobValue() in C:\Users\User\Source\Workspaces\TFS\Dev\Assemblies\BusinessObjects\Entities\ClaimPhoto.cs:line 530
at ELinkMvc.Controllers.PhotoController.d__62.MoveNext() in C:\Users\USer\Source\Workspaces\TFS\Dev\Web\ELinkMvc\ELinkMvc\Controllers\PhotoController.cs:line 1386
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass8_0.b__1(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_0.b__0()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_2.b__2()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass11_2.b__2()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass3_6.b__4()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass3_1.b__1(IAsyncResult asyncResult)

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Identity:0.4440233,Storage:0.19851191,Service Bus:0.12424685'

Hi @mike-sherrane.   Thank you for reaching out and we regret that you're experiencing difficulties.   To clarify:

Azure.Core version 1.25 depends on System.Text.Json >= 4.7.2.
Version 1.4.1 (there is no version 1.14, so I'm assuming it was a typo) depended on System.Text.Json >= 4.6.

From the error that you're seeing, it would appear that there are dependency conflicts either with other dependencies or the application itself.   I'd suggest adding a direct reference to System.Text.Json version 4.7.2 or greater and testing with that.
If you'd be so kind as to share your .csproj file - specifically all of its references, it would help us to offer further thoughts.

Thank you for your quick response.
I am aware Azure.Code 1.25.0 requiresa System.Text.Json 4.72 or greater, which is why I was greatly surprised by the error.  I have version <IP_ADDRESS> in the project reference.
This is the project file:

Debug
AnyCPU

2.0
{12415206-7C69-42A1-8812-C454CB68559B}
{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}
Library
Properties
ELinkMvc
ELinkMvc
v4.8
false
false

SAK
SAK
SAK
SAK

true
full
false
bin\
TRACE;DEBUG
prompt
4
7.2

pdbonly
true
bin\
TRACE
prompt
4

      $(MSBuildWarningsAsMessages);MSB3274;MSB3275;MSB3268

21.2.8

6.22.0

6.0.0

4.3.1

..\..\..\packages\System.IO.4.3.0\lib\net462\System.IO.dll
True
True

..\..\..\packages\Microsoft.Net.Http.2.2.29\lib\net45\System.Net.Http.Extensions.dll

..\..\..\packages\System.Runtime.4.3.0\lib\net462\System.Runtime.dll
True
True

..\..\..\packages\System.Security.Cryptography.Encoding.4.3.0\lib\net46\System.Security.Cryptography.Encoding.dll
True
True

..\..\..\packages\System.Security.Cryptography.Primitives.4.3.0\lib\net46\System.Security.Cryptography.Primitives.dll
True
True

Global.asax

Web.config

Web.config

Designer

Designer

{f8a254cb-a0a2-4c91-beb3-bbffcaf35ffe}
Custard.BusinessObjects.DocumentCenter

{2005e518-964b-4129-a5fa-621024b20c2b}
Custard.BusinessObjects

{f382372c-0565-46c9-a195-a9120d8c8387}
Custard.Classes

{0796da63-8b7c-4b9a-b7e6-7d67c75f2301}
Custard.Word.OpenXml

{5783a30d-c6df-476a-88d9-97f13d34c18e}
Custard.Reporting

{fb2548e0-1c73-4a55-96c7-af86371b0526}
Custard.UtilitiesWindows

{a731147d-ac2d-4838-91ff-979b5a4793dc}
Custard.Utilities

10.0
$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)

True
True
52254
/
http://localhost/ELinkMvc>
          False
False

False

This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}.

From: Jesse Squire @.>
Sent: Tuesday, August 9, 2022 8:31 AM
To: Azure/azure-sdk-for-net @.>
Cc: Sherrane, Michael @.>; Mention @.>
Subject: [External] Re: [Azure/azure-sdk-for-net] Azure.Core, Version=1.25 is trying to load System.Text.Json, Version=<IP_ADDRESS> (Issue #30414)
[External – This email is coming from outside of Custard Insurance Adjusters, Inc. DO NOT CLICK LINKS or OPEN ATTACHMENTS unless you recognize and trust the sender]
Hi @mike-sherranehttps://github.com/mike-sherrane. Thank you for reaching out and we regret that you're experiencing difficulties. To clarify:

Azure.Core version 1.25 depends on System.Text.Json >= 4.7.2.
Version 1.4.1 (there is no version 1.14, so I'm assuming it was a typo) depended on System.Text.Json >= 4.6.

From the error that you're seeing, it would appear that there are dependency conflicts either with other dependencies or the application itself. I'd suggest adding a direct reference to System.Text.Json version 4.7.2 or greater and testing with that.
If you'd be so kind as to share your .csproj file - specifically all of its references, it would help us to offer further thoughts.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/30414#issuecomment-1209320280, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2OC2I234B3QN4UQGX7FBPLVYJFPTANCNFSM56ACTYRA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Thanks for the additional context.   I cannot explain the binding behavior yet; we'll need to dig a bit into that in order to understand, given the complexity of assembly binding in the desktop framework.
If I create a new .NET Framework MVC project for net48 and add the full set of your references, I am seeing a compiler warning about the same version conflicts that you're reporting for System.Text.Json.  It's worth noting that I'm also seeing the version conflict warning for a handful of other assemblies, many of which are not dependencies of the Azure SDK packages, such as Newtonsoft.Json.
Example:
Consider app.config remapping of assembly "System.Text.Json, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" to Version "<IP_ADDRESS>"
... SNIP ... to solve conflict and get rid of warning.

However, if I create a new MVC project on net48 and add only references to the Azure SDK packages and System.Text.Json v6.0.5, I do not receive any warning or version conflicts.  That leads me to believe there may be some version conflicts that exist somewhere in the set of references that you're using.
Following the guidance in that warning to add a binding redirect cleared up the compiler issue for me and I'm able to interact with Blob Storage while running.
<dependentAssembly>
  <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" />
  <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
</dependentAssembly>

Would you be so kind as to test with a binding redirect and let us know the results?

Thank you for your insights.  All the assemblies have the recommended directive in their app.config files as well as it residing in the web.config of the application prior to me contacting you.  This is a very old project (originally MVC 3 app) that was slated to get reworked in the future.  It sounds like we may need to perform this task sooner rather than later.  Were you able to identify any libraries that generated the warnings?  I have removed / reinstalled most of the packages.
FWIW, we do have these libraries functioning in an API.  I made sure all the packages were on consistent versions (each app has libraries the other doesn’t).  So your report makes me believe I will need to generate a new project.
Thank you
From: Jesse Squire @.>
Sent: Tuesday, August 9, 2022 11:52 AM
To: Azure/azure-sdk-for-net @.>
Cc: Sherrane, Michael @.>; Mention @.>
Subject: [External] Re: [Azure/azure-sdk-for-net] Azure.Core, Version=1.25 is trying to load System.Text.Json, Version=<IP_ADDRESS> (Issue #30414)
[External – This email is coming from outside of Custard Insurance Adjusters, Inc. DO NOT CLICK LINKS or OPEN ATTACHMENTS unless you recognize and trust the sender]
Thanks for the additional context. I cannot explain the binding behavior yet; we'll need to dig a bit into that in order to understand, given the complexity of assembly binding in the desktop framework.
If I create a new .NET Framework MVC project for net48 and add the full set of your references, I am seeing a compiler warning about the same version conflicts that you're reporting for System.Text.Json. It's worth noting that I'm also seeing the version conflict warning for a handful of other assemblies, many of which are not dependencies of the Azure SDK packages, such as Newtonsoft.Json.
Example:
Consider app.config remapping of assembly "System.Text.Json, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" to Version "<IP_ADDRESS>"
... SNIP ... to solve conflict and get rid of warning.
However, if I create a new MVC project on net48 and add only references to the Azure SDK packages and System.Text.Json v6.0.5, I do not receive any warning or version conflicts. That leads me to believe there may be some version conflicts that exist somewhere in the set of references that you're using.
Following the guidance in that warning to add a binding redirect cleared up the compiler issue for me and I'm able to interact with Blob Storage while running.

Would you be so kind as to test with a binding redirect and let us know the results?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/30414#issuecomment-1209567256, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2OC2IYGDWNFJLWEU3CK7QLVYJ5CFANCNFSM56ACTYRA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

For my test app, the full set looks like:
1>  Consider app.config remapping of assembly "Microsoft.Bcl.AsyncInterfaces, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.Extensions.DependencyInjection, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.Extensions.DependencyInjection.Abstractions, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Abstractions, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Protocols, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Protocols.OpenIdConnect, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Tokens, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Newtonsoft.Json, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Buffers, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Diagnostics.DiagnosticSource, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.IdentityModel.Tokens.Jwt, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Memory, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" ... SNIP ... to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Runtime.CompilerServices.Unsafe, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Text.Json, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.

The recommendation for mitigation is:
warning MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this
warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the
application configuration file:

<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Extensions.DependencyInjection" culture="neutral" publicKeyToken="adb9793829ddae60" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.Extensions.DependencyInjection.Abstractions" culture="neutral" publicKeyToken="adb9793829ddae60" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.IdentityModel.Abstractions" culture="neutral" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.IdentityModel.Protocols" culture="neutral" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.IdentityModel.Protocols.OpenIdConnect" culture="neutral" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Microsoft.IdentityModel.Tokens" culture="neutral" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="Newtonsoft.Json" culture="neutral" publicKeyToken="30ad4fe6b2a6aeed" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Buffers" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Diagnostics.DiagnosticSource" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.IdentityModel.Tokens.Jwt" culture="neutral" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Memory" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>
<assemblyBinding
  xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Text.Json" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />
    <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
  </dependentAssembly>
</assemblyBinding>

Thank you for your time and patience.  I have all of these declarations.  One of the assemblies is misbehaving and trying to load System.Text.Json <IP_ADDRESS> and was hoping you had a tool that could determine which is the offender.  If not, there is no reason to continue.   Thank you.
From: Jesse Squire @.>
Sent: Tuesday, August 9, 2022 3:37 PM
To: Azure/azure-sdk-for-net @.>
Cc: Sherrane, Michael @.>; Mention @.>
Subject: [External] Re: [Azure/azure-sdk-for-net] Azure.Core, Version=1.25 is trying to load System.Text.Json, Version=<IP_ADDRESS> (Issue #30414)
[External – This email is coming from outside of Custard Insurance Adjusters, Inc. DO NOT CLICK LINKS or OPEN ATTACHMENTS unless you recognize and trust the sender]
For my test app, the full set looks like:
1>  Consider app.config remapping of assembly "Microsoft.Bcl.AsyncInterfaces, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.Extensions.DependencyInjection, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.Extensions.DependencyInjection.Abstractions, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Abstractions, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Protocols, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Protocols.OpenIdConnect, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Microsoft.IdentityModel.Tokens, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "Newtonsoft.Json, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Buffers, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Diagnostics.DiagnosticSource, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.IdentityModel.Tokens.Jwt, Culture=neutral, PublicKeyToken=31bf3856ad364e35" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Memory, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" ... SNIP ... to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Runtime.CompilerServices.Unsafe, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
1>  Consider app.config remapping of assembly "System.Text.Json, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" from Version "<IP_ADDRESS>" [] to Version "<IP_ADDRESS>" ... SNIP ... to solve conflict and get rid of warning.
The recommendation for mitigation is:
warning MSB3247: Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this
warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the
application configuration file:
<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.Extensions.DependencyInjection" culture="neutral" publicKeyToken="adb9793829ddae60" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.Extensions.DependencyInjection.Abstractions" culture="neutral" publicKeyToken="adb9793829ddae60" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.IdentityModel.Abstractions" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.IdentityModel.Protocols" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.IdentityModel.Protocols.OpenIdConnect" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Microsoft.IdentityModel.Tokens" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="Newtonsoft.Json" culture="neutral" publicKeyToken="30ad4fe6b2a6aeed" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.Buffers" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.Diagnostics.DiagnosticSource" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.IdentityModel.Tokens.Jwt" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.Memory" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

<assemblyBinding
xmlns="urn:schemas-microsoft-com:asm.v1">

<assemblyIdentity name="System.Text.Json" culture="neutral" publicKeyToken="cc7b13ffcd2ddd51" />

<bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />

—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/30414#issuecomment-1209796066, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2OC2IZTSQ4VD7V6DU3DPNTVYKXNZANCNFSM56ACTYRA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

hoping you had a tool that could determine which is the offender.

Unfortunately, there's nothing available internally to us that isn't also public.  In this case, we'd normally recommend fuslogvw, but this discussion started with Fuse logs, so I'm kind of at a loss.  If the binding redirects aren't doing their job, the only thing that occurs to me is to start pulling out references and see if we can isolate the culprit.
Per your request, I'll mark this as addressed for now.  I've got an inquiry out internally to see if folks with more depth on assembly binding internals have a suggestion.   If anything comes of that, I'll follow-up here.  Please also feel free to unresolve if you'd like to continue the discussion.

Thank you for your time and  patience Jesse,
I have been doing as you suggested for the past week.  As I stated previously, we have an API that is functioning fine with these libraries.  I removed all the libraries the MVC app uses that the API does not (excluding OWIN) with no luck.  I can only read BLOBS by reverting my MVC app to Azure.Core <IP_ADDRESS>, Azure.Storage.Common <IP_ADDRESS>, and Azure.Storage.Blobs <IP_ADDRESS>, but that is no solution.
Mike
From: Jesse Squire @.>
Sent: Wednesday, August 10, 2022 10:49 AM
To: Azure/azure-sdk-for-net @.>
Cc: Sherrane, Michael @.>; Mention @.>
Subject: [External] Re: [Azure/azure-sdk-for-net] Azure.Core, Version=1.25 is trying to load System.Text.Json, Version=<IP_ADDRESS> (Issue #30414)
[External – This email is coming from outside of Custard Insurance Adjusters, Inc. DO NOT CLICK LINKS or OPEN ATTACHMENTS unless you recognize and trust the sender]
hoping you had a tool that could determine which is the offender.
Unfortunately, there's nothing available internally to us that isn't also public. In this case, we'd normally recommend fuslogvw, but this discussion started with Fuse logs, so I'm kind of at a loss. If the binding redirects aren't doing their job, the only thing that occurs to me is to start pulling out references and see if we can isolate the culprit.
Per your request, I'll mark this as addressed for now. I've got an inquiry out internally to see if folks with more depth on assembly binding internals have a suggestion. If anything comes of that, I'll follow-up here. Please also feel free to unresolve if you'd like to continue the discussion.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/30414#issuecomment-1210783217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2OC2I5Q4EPEYCXB56FAEPDVYO6MJANCNFSM56ACTYRA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Issue in downloading PDF

While using the latest jspdf & html2pdf js files, downloading the pdf from any browser(here i used chrome). In my HTML i have 15 pages (while downloading data visible all blank pages). I Tested with different trials then upto 7 pages html we can view download as pdf. Above 7 pages we are getting blank pages.Can anyone resolve this. please update.

Hi @bangararaju, are you using the version of html2canvas available in the vendor folder of this package? It has some additional bugfixes, including one that I think resolves your issue. See the readme for a bit more info.

Hi @eKoopmans, using the above vendor folder docs and below the reference using for html2pdf.js
( https://rawgit.com/eKoopmans/html2pdf/master/src/html2pdf.js).After using this files in chrome its working. where as in IE browser (IE10 & above) get the error- promise issue (it's in CDN only) .Can anyone get this type of issue.

Hi, yes html2canvas relies on Promises, which are supported natively in modern browsers, but older browsers (like IE) require a polyfill. See the html2canvas readme for more info.

@eKoopmans  the link above to the ' html2canvas readme' is a dead link, can you post another?

Oops, I totally missed your comment @iammikek! Very sorry. I've fixed the link in my original comment.


proposal: http: FileServer: add json content type for directory serving

Repost of golang/go#23898 for continued conversation.

Proposal for the http.FileServer:
In case that the Accept request header contains application/json, and the path leads to a directory, return the content of a directory as JSON.
Reason: add a bot an easier way to parse directory content.
Similar to: NGINX has autoindex_format option that has a json argument which makes NGINX return directory listings in a json format. The returned format is a list of maps, each map contains name, type (directory/file), mtime (modify time) and files also contain size in bytes, for example:
[
{ "name":"c", "type":"directory", "mtime":"Sun, 21 Jan 2018 08:13:49 GMT" },
{ "name":"xxx", "type":"file", "mtime":"Sun, 21 Jan 2018 08:13:49 GMT", "size":17 }
]

Doesn't mean that this is a good representation, we can debate if we want to adopt it.

TODO

Create separate package
Respond with the correct content type based on the Accept header

@posener check out the package in the previous comment and please provide feedback.

@jasonwbarnett it is hard to understand what are your changes on top of the standard library code.
Can you provide all your changes in a single commit?
Or maybe find a way so this code can be easily rebased on top of changes committed to the standard library?

@posener updated to maintain history (although it's not easily rebasable) https://github.com/jasonwbarnett/jsonfs/commit/7a6383a98b6a87ea0130a13d14f2c930ac420ae9

Nice code,
I've posted some comments there, hope you can view them.
I would also rename the package, maybe fileserver or something like that, so Instead of http.FileServer() it will be fileserver.New().
The README is nice,
I would change it to the diff syntax:
func main() {
	// Simple static webserver:
-	log.Fatal(http.ListenAndServe(":8080", http.FileServer(http.Dir("/usr/share/doc"))))
+	log.Fatal(http.ListenAndServe(":8080", fileserver.New(http.Dir("/usr/share/doc"))))
}

:+1:

Thank you, check out the updates: https://github.com/jasonwbarnett/jsonfs/commit/113034adee9a19c09880ab99812bc33618e74670
I agree with the API change :) -- I'll rename the package shortly.

@posener Thanks for your feedback. I updated the code appropriately and the API change is done also. See the latest commits to https://github.com/jasonwbarnett/jsonfs/commits/master.

Nice.
No need for the src and fileserver subfolders.
Just rename the project to fileserver, and put the code in the root directory of the project.

@posener I was thinking about that but didn't want there to be some other package that was needed and I wanted clean organization, but obviously your suggestion is the most idiomatic go thing to do. I'll rename now!

@posener I hesitated to do this for some reason, but I think you're right. https://github.com/jasonwbarnett/fileserver

It looks to me like a lightweight and elegant change!
Rebasing this library over the standard library is a hard thing - I can see it useful to get into the standard library.
It is a shame they didn't want it...
Great job @jasonwbarnett !

I could easily automate the rebasing on top of the standard library (assuming no merge conflicts) with a lambda or something. I might look into that and I want to add some tests too.
Thanks for your help and review of the code.


Text.destroy crashes Chrome tab

I try to clean memory after removing a text objects. I call:
textObject.destroy(true);
but it crashes the Chrome tab if I call it on many text objects at once.
Maybe I do that incorrectly? After reading PIXI source I see that PIXI creates a html canvas object for every text instance, is it necessary?

Hello! Just tested this demo on v3. Seemed to work fine now :+1:
I would suggest that if you use that much text it may be best to reuse the texture if the text is the same. Alternatively using bitmap text would also be a good path. thanks!


fix(Tab): activeTabIndex always updating automatically

Before:

After:

Seems reasonable. Thanks for the gif. I assume that the "Always 1" tab is the thing you were fixing?

@jamesmfriedman Yeah, the "Always 1" tab was the bit being fixed.

Thanks for doing this, will go out in the next release.


adding max_tokens to cli

Adding max tokens to cli as using gpt3.5 crashes when the context length is 10k

@ctr26 This will be solved with #2 - we'll have a mapping of model -> context window (max tokens) and we'll break down files and prompts accordingly.

Ааа

I don't have access to gpt-4-32k. How can I use gpt-4? I get this error even with these changes
openai.error.InvalidRequestError: This model's maximum context length is 8192 tokens. However, you requested 10601 tokens (601 in the messages, 10000 in the completion). Please reduce the length of the messages or completion.

        max_tokens: int = typer.Option(8192),
    ):

    ai = AI(
        model=model,
        temperature=temperature,
        max_tokens=int(max_tokens),
    )

@gianpaj The output also contributes to the number of tokens. If your model has a max context window of 8k, you're probably better off making max_tokens 4k or so.

vvdd

Is it also possible to also add something that can change the openai base url? So this could work with the microsoft azure openai endpoint or proxies

@Ran-Mewo Yes definitely, I'll try to get to this later - feel free to also submit a PR for this if you'd like


Some paths from the generated docs don´t exist for the build! macro.

The path in the documation for OWNER_SECURITY_INFORMATION,  Windows::Win32::System::Services::OWNER_SECURITY_INFORMATION is not reachable for the build! macro.
Is there a way to find the right path without the generated docs ? Because Windows::Win32::Security::Authorization::SE_FILE_OBJECT is also not reachable.

Looks right to me, are you on the latest crate? (0.18)

Yes i use 0.18. I also tryed to build my binding crate seperate from the main programm with cargo to exclude proplems that can accure with the rust-analyzer, sometimes. The paths are directly copied from the docs.

I can reproduce this.

git clone https://github.com/riverar/repo-b40a59d6
cargo build

To unblock, you could widen your selection:
windows::build! {
    Windows::Win32::System::Services::*,
    Windows::Win32::Security::Authorization::*
};

The metadata defines these values as unscoped enum values. It basically groups these constants into types but they were never intended to be used as types (C style enums are weakly typed and often they weren't enums at all) but the build macro has to make the best of this situation. What you can do is import SE_OBJECT_TYPE and OBJECT_SECURITY_INFORMATION respectively and it will define all of the constants in the surrounding module. This is by design but I should add an FAQ for this.

Closing as Windows::Win32::System::Services::OBJECT_SECURITY_INFORMATION, et al, works.


[stable/gitlab-ce] Removing the icon as it is not accessible

The icon is causing errors from the Artifact Hub so removing

Merging as this is a long ago deprecated chart and the only change is to remove the icon.


Removing only the icon

Is it possible to remove the icon of tkinter only?

Right now, the library doesn't have any feature to remove the icon of tkinter only, but I might add something like that in the future releases.
Possible Workaround - Set a transparent PNG as the app icon


Provide some more examples

Hi can you provide some more examples please?
Like if I want to switch to 1 fragment to another from a button click in Fragment1 I want to go to Fragment2, so I've used activity for replacement logic.
In Activity I've
@Subscribe(tags = {@Tag(RxConstants.EventType.SCREEN_SWITCH_EVENT)})
In Activity I'm adding Fragment1 by
@Produce(tags = {@Tag(RxConstants.EventType.SCREEN_SWITCH_EVENT)})
private Screen getRegisterScreen() {
return Screen.REGISTER;
}
Now in Fragment1 on the click of a Button I want to replace Fragment1 with Fragment2.
So in Fragment2 I'm doing something like this:
@Produce(tags = {@Tag(RxConstants.EventType.SCREEN_SWITCH_EVENT)})
private VehicleActivity.Screen getListingScreen() {
return VehicleActivity.Screen.VEHICLE_LISTING;
}
But when it will be executed? As I want it to execute on the click of a button.
So can you please guide me with the same?

I got it, .post() is there for this.
Can you please add the same in Readme.md and your sample app.

you can find the usage/example here: app

Have already gone through the app and it doesn't cover post() and your ReadMe covers the @Annotations only. Just a suggestion to provide a more detailed sample.

Mmm, I have add this to RxBus/README.md at master · AndroidKnife/RxBus.
It also used in demo, here: RxBus/MouseMam.java at master · AndroidKnife/RxBus

I thing I'm not clear with,
Do I need to register/unregister in all the classes where I'm using @subscribe, @produce .post or only where I use  @subscribe, @produce .
Also I've an activity and I'm doing
RxBus.get().post(BusAction.EAT_MORE, this);
and there there is a dialog somewhere where I'm doing
@Subscribe(tags = {@Tag(BusAction.EAT_MORE)})
subscribeMe(Object obj) {
// the code is never reaching here. So not able to get this obj
}
I've done register and unregister in both activity and dialog.
So anyway to diagnose this issue by any logging or maybe I'm doing something wrong?

Only where you use the annotation( @subscribe and @produce), you should register/unregister the class.
You post the activity, but while you want to receive an object, so it can't receive the post. you should make sure that you post the Cat, and you also want to receive the Cat (not Mouse).

Sorry that example was copied from your post only from different places, have updated the example.
So here is my scenario :
Activity A --> Posts an Obj... Then Activity B--> Open a Dialog in in Activity B and tried to @Subscribe the Obj in the Dialog. But not getting anything...

Only the subscribed object can receive the post object, so please make sure that you have subscribe the object and then post the data.

I checked out your sample as well as ReadMe but did not understand it properly, so have created a demo project where I tried to mock my real scenario as much as possible. https://github.com/ShivamDev31/RxBusDemo
Maybe you can tell me now what I'm doing wrong.

If you have fix the issue, please close this issue.


ERC-1400 doesn't exist

This proposal was never merged as an actual EIP. See https://eips.ethereum.org/EIPS/eip-1400 (or the lack thereof).
I recommend not depending on the behavior of this project, as it is NOT standardized.
If you are technically inclined, feel free to reach out to me, and I'd be happy to walk you through the process of creating and moving an EIP to Final.

what should be the standard that should be used to issue tokens for security tokens currently whats the most popular standard

what should be the standard that should be used to issue tokens for security tokens currently whats the most popular standard

ERC-20, ERC-721, or ERC-1155


Deleting a Provider should not delete associated RawNotifications and ParsedNotifications

Environment

Nautobot version: 1.1.4
nautobot-circuit-maintenance version: 0.3.2

Expected Behavior
On deleting a Provider, circuit-maintenance records should not be auto-deleted, although any references to that Provider should be nulled out.
Observed Behavior
Deleting a Provider deletes all of its associated RawNotifications and ParsedNotifications, although CircuitMaintenances remain present since they are linked to Circuits rather than Providers.
Steps to Reproduce
This happened in a user environment where, due to provider mergers and name changes, we had multiple Provider records that actually referred to the same company. After migrating all relevant Circuits to the correct single, consolidated, Provider record, I deleted the old Provider which no longer had any associated Circuits. To my surprise, this also deleted a slew of older RawNotifications and ParsedNotifications as they were associated to the old Provider still. The result is that I still have valid CircuitMaintenance records (since the Circuits were not deleted and are now associated to the new provider) but no longer any references to the parsed data that originated these records.
I would have preferred for the old RawNotification and ParsedNotification records to remain available, presumably with null provider references, rather than being deleted.

I agree, let's do it.


Feature/per file ignores

resolves #241
This PR implements per-file-ignores as a per-path built filter for the output of crate::linter::check_path.
The goal is feature parity.
Caveats
There is definitely room for optimisation here. Currently filtering the output by removing checks to ignore, after they've been checked leaves the obvious improvement of not executing the check in the first place. This is fairly intrusive on the current approach to the Checker as settings.selected is used ubiquitously as the source for code checking.
Additionally, all pairs are matched against each entry to generate the set of ignores to filter against. It's possible to use a better representation of these patterns such that iterating over the each match is possible (although this still has a worst case of O(n)).
Errors for incorrect pattern:code pairs currently fail silently in config, and fail with the corresponding anyhow message dumped to stdout. This behaviour is potentially debatable and feedback would be appreciated.
Description
Per file ignores is available from both the cli via --per-file-ignores=<stuff> and in the pyproject.toml under tool.ruff.per-file-ignores. Additionally the cache-key is generated using per-file-ignores, as changes to the setting leads to a different output that  couldn't be represented by the previous cache-key generation

Awesome! Excited to review. Thanks for putting this together.

Currently filtering the output by removing checks to ignore, after they've been checked leaves the obvious improvement of not executing the check in the first place. This is fairly intrusive on the current approach to the Checker as settings.selected is used ubiquitously as the source for code checking.

Yeah, I think the approach you took is good. We should likely be filtering checks at the end regardless. The fact that we avoid including erroneous checks by checking Settings everywhere should be viewed more as an optimization (though the code currently relies on it).

This is great! Thank you. I left a variety of comments. If you're able to address them, it'd be much appreciated. If you'd rather not, I'd understand and can also take over, adjust, and merge -- totally up to you.

Resolved the comments, I suspect there may be areas still to clean up for semantic purposes (e.g. struct locations), feel free to edit as needed

Awesome, thank you, will review and merge today!

Once this is merged, I'll cut 0.0.46.


chore: use sucrase

I did some tests using @sucrase/plugin and it turned out to be much faster than babel
It also managed to transpile the node_modules folder, but it took a little longer.
Maybe it will solve #132, just adding :
transformIgnorePatterns: []

What do you think? @pi0