text:
[BUG] Occasional UnauthorizedAccessException from AmqpServiceClient.GetRuntimeInformationAsync

Library name and version
Microsoft.Azure.EventHubs (via Functions extension v4)
Describe the bug
Hi,
Since a few months back we're getting quite a lot, but not solely, exceptions in our function apps. (Started on November 7th, been running fine for a long time before that)
The functions are starting up and functioning, so probably a retry mechanism eventually succeeds - but what is this and what can we do about it?
It's spamming our logs, and we're unsure about the impact on the functionality.
The credentials are fine.
Thank you!
The stack trace that we're seeing in the logs:
2022-01-12T10:15:20.759 [Error] The listener for function 'CalculateCpuProcessor' was unable to start.Microsoft.Azure.WebJobs.Host.Listeners.FunctionListenerException : The listener for function 'CalculateCpuProcessor' was unable to start. ---> Microsoft.Azure.EventHubs.Processor.EventProcessorConfigurationException : Encountered error while fetching the list of EventHub PartitionIds ---> System.UnauthorizedAccessException : Unauthorizedat async Microsoft.Azure.EventHubs.Amqp.Management.AmqpServiceClient.GetRuntimeInformationAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.EventHubClient.GetRuntimeInformationAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.Processor.PartitionManager.GetPartitionIdsAsync()End of inner exceptionat async Microsoft.Azure.EventHubs.Processor.PartitionManager.GetPartitionIdsAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.Processor.PartitionManager.GetPartitionIdsAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.Processor.PartitionManager.InitializeStoresAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.Processor.PartitionManager.StartAsync()at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.EventHubs.Processor.EventProcessorHost.RegisterEventProcessorFactoryAsync(??)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.EventHubs.EventHubListener.StartAsync(CancellationToken cancellationToken)at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()at async Microsoft.Azure.WebJobs.Host.Listeners.FunctionListener.StartAsync(??) at C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Listeners\FunctionListener.cs : 68End of inner exception
We have a function app with ~20 functions, many of them have input and output bindings as such:
        public async Task CalculateCpuProcessor(
            [EventHubTrigger("%EventHubName%", Connection = "EventHubConnection", ConsumerGroup = "calculatecpu")] EventData[] events,
            [EventHub("%EventHubName%", Connection = "EventHubConnection")] IAsyncCollector<string> outputEvents)

And in Azure we have appsettings like:

Expected behavior
No Unauthorized exceptions
Actual behavior
Lots of exceptions in the logs
Reproduction Steps
I'd be happy to provide you with any information you ask for :)
Environment
.net6
functions_extension_version ~4
Azure function app
EP1 app service plan

Adding more info to this, we have 4 environments - and it's only one of them that has this shown this Exception - very weird.
Any insight on what's throwing this exception would be great, and if it's been seen in Azure Functions with binding triggers before.

@andyhammar Do you have any vnet integration enabled in your Azure Function.  If yes, I suspect vnet integration was not completed successfully hence you are getting these errors.
Also, can you please check for any info / exceptions by going to your function app > Diagnose and solve problems > Availability and Performance > Function App Down or Reporting Errors to look for any specific errors.

Hi @SaurabhSharma-MSFT ,
The function app does not have vnet integration enabled.
Thanks for the pointer to diagnostics. I hadn't seen that UI before, but we're pro-active about checking AppInsights traces and exceptions, so the errors surfaced are the ones that we're investigating already, including this one.
What we're not understanding is why we're seeing this now and then, but not always - and that the function app is doing what it's supposed to. (we have a few timer triggered functions, but most of them are event-hub triggered).
Could this have to do with EventHub load/connections?
Is the FunctionListener retrying the action and this is "just" a warning? We could ignore it if so (filter out), but I want to understand why fully first.
From the diagnostics UI, I can find this error:

and it's pattern is somewhat irregular:

@andyhammar I believe this has to do with the EventHub connections as we get issues when the underlying EventHub connection changes.  Did this EventHub fail happens in the past as well?   I believe you may need to check with the Azure Support team by creating a Support ticket as they may have access to the underlying EventHub logs to further investigate.  Please let me know in case you have any limitations opening a ticket.
Thanks

Hi @SaurabhSharma-MSFT. Don't think it happened before Nov 7th, or that's just the AppInsights retention cutoff :)
But, we've upgraded lib and also started scaling the event hub out, and not seen for a while - so I'm fine with closing this issue now. I'll raise a support ticket if we start seeing it again.
Thanks!

authors: SaurabhSharma-MSFT andyhammar


text:
[BUG] Unable to use AuthorizationManagementClient due to preview api use

Library name and version
Microsoft.Azure.Management.Authorization 2.0.13.preview
Describe the bug
Trying to add a role assignment but unable to use AuthorizationManagementClient to do anything.
The library has been in preview for the last 5 years and each preview release used a release of the Azure preview API which subsequently got dropped in lieu of a properly dated library version.
If I drop to 2.0.1 which is the last stable release from 2017 I can't use with .net core.
Can you let me know when there will be another stable release of this library? For now I'm dropping back to the REST API.
Expected behavior
Adds role assignment to an Azure object
Actual behavior
Response produces:
{"error":{"code":"InvalidApiVersionParameter","message":"The api-version '2020-08-01-preview' is invalid. The supported versions are '2022-05-01,2022-03-01-preview,2022-01-01,2021-04-01,2021-01-01,2020-10-01,2020-09-01,2020-08-01,2020-07-01,2020-06-01,2020-05-01,2020-01-01,2019-11-01,2019-10-01,2019-09-01,2019-08-01,2019-07-01,2019-06-01,2019-05-10,2019-05-01,2019-03-01,2018-11-01,2018-09-01,2018-08-01,2018-07-01,2018-06-01,2018-05-01,2018-02-01,2018-01-01,2017-12-01,2017-08-01,2017-06-01,2017-05-10,2017-05-01,2017-03-01,2016-09-01,2016-07-01,2016-06-01,2016-02-01,2015-11-01,2015-01-01,2014-04-01-preview,2014-04-01,2014-01-01,2013-03-01,2014-02-26,2014-04'."}}
Reproduction Steps
Something like this.

Generate a bearer token
Use the AuthorizationManagementClient
Assign a role definition (contributor used below)
Watch is blow up with: "code":"InvalidApiVersionParameter","message":"The api-version '2020-08-01-preview' is invalid

var credentials = new TokenCredentials(await GetAccessTokenFor(resourceUriAzure,_tenantName, _tenantId, _clientId, _clientSecret));
var client = new AuthorizationManagementClient(credentials);
var assignment = await client.RoleAssignments.CreateByIdAsync(resourceId, new Microsoft.Azure.Management.Authorization.Models.RoleAssignmentCreateParameters()
{
PrincipalId = userName,
PrincipalType = "User",
RoleDefinitionId = "b24988ac-6180-42a0-ab88-20f7382dd24c"
});
Environment
.net 6
windows 11
Visual Studio 2022

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'ARM:0.18391359,Resource Authorization:0.08880011,Storage:0.04429862'

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@azurecoder please try with our new generation of .NET SDK: https://www.nuget.org/packages/Azure.ResourceManager.Authorization/1.0.0
Here is a quick start guide: https://github.com/Azure/azure-sdk-for-net/blob/main/doc/dev/mgmt_quickstart.md

source: gharchive/issue

authors: azure-sdk azurecoder fengzhou-msft jsquire

repo: Azure/azure-sdk-for-net

license: MIT

license_type: permissive

license_source: github-api


text:
Cannot update Data Transparent Data Encryption State

Library name and version
Azure.ResourceManager.Sql 1.1.0
Describe the bug
I am trying to update data transparent data encryption state from C# code. However, i can not update due to NullReferenceException thrown from inside package:

My step is only getting it from azure resource and update state property to enable/disable it.
Expected behavior
Can enable/disable data encryption
Actual behavior
Throw NullReferenceException
StackTrace:
at Azure.ResourceManager.Sql.LogicalDatabaseTransparentDataEncryptionResource.d__16.MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
Reproduction Steps

Retrieve logicalDatabaseTransparentDataEncryption
set state = enable/disable
Call  logicalDatabaseTransparentDataEncryptionResource.UpdateAsync with data above: logicalDatabaseTransparentDataEncryption

Environment
NET SDK (reflecting any global.json):
Version:   6.0.300
Commit:    8473146e7d
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19044
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\6.0.300\
Host (useful for support):
Version: 6.0.5
Commit:  70ae3df4a6
.NET SDKs installed:
2.1.818 [C:\Program Files\dotnet\sdk]
6.0.300 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Thank you for your feedback, we will check it.

The root cause of the issue is that in swagger definition of the TransparentDataEncryptions_CreateOrUpdate operation, it's not marked as an LRO (long running operation). Therefore, the SDK code generated based on the wrong swagger does not handle the response correctly. This should be fixed on the service swagger, then we can regenerate the SDK based on fixed swagger.

Seeing same issue.

As described in https://github.com/Azure/azure-sdk-for-net/issues/33170#issuecomment-1386991512, this needs the service team to fix the swagger.

SDK team can't do anything here, have created S360 for Sql team to follow up.


text:
Fluent: missing ability to create a disk from a platform image?

I can't seem to find any fluent API way to execute this REST API to create a new managed disk from an existing platform image:
PUT
/subscriptions/{subscriptionId}/resourceGroupName/{resourceGroup}/providers/Microsoft.Compute/disks/{diskName}?api-version={api-version}
--
{
  "name": "myManagedDisk1",
  "location": "West US",
  "properties": {
    "osType": "Windows",
    "creationData": {
      "createOption": "FromImage",
      "imageReference": {
        "id": "/Subscriptions/{subscriptionId}/Providers/Microsoft.Compute/Locations/uswest/Publishers/Microsoft/ArtifactTypes/VMImage/Offers/{offer}"
      }
    }
  }
}

All I can see are options to create the disk from existing VHD, an existing managed disk, or an existing snapshot.
(feedback based on "Microsoft.Azure.Management.Compute.Fluent" version="1.1.3")

@TimLovellSmith
Fluent layer intentionally hide this option. Once we create a managed disk using FromImage with a platform image as source, the only way to use that disk as OS Disk is via "Attach" option. When VM is created with "Attach" option platform will boot the VM as is, without specializing the VHD, this means user won't be able to set user credentials for the VM. At this point VM is un-usable. "FromImage" is used by compute resource provider internally as part of creation of VM with implicit managed disk.
Could you let us know the end-to-end scenario you are trying to achieve with this option?

@anuchandy
I see. I guess you're right that it could confuse people just trying to do the most basic thing (create a VM). FWIW, I was trying to implement a scenario where I would just download the nonspecialized VHD to see if I can manipulate it, and then turn it into a new image. Currently I am working around by just forming the HTTP request myself. So its no big deal for me.

@TimLovellSmith if the non-specialized (generalized) VHD is stored in a storage account then you can create a custom image by pointing to it (without downloading it). Something like:
var image = azure.VirtualMachineCustomImages.Define(`<image-name>`)
        .WithRegion(Region.USEast)
        .WithNewResourceGroup(`new-resource-group-name`)
        .WithLinuxFromVhd(`url-to-your-vhd`, OperatingSystemStateTypes.Generalized)
        .WithOSDiskCaching(CachingTypes.ReadWrite)
        .Create();

@anuchandy manipulation being the key word :)

authors: TimLovellSmith anuchandy


text:
[BUG] OpenAI: Unsupported parameter

Library name and version
Azure.AI.OpenAI 2.1.0-beta.1
Describe the bug
Setting MaxOutputTokenCount cause API call error with o1 model:
System.ClientModel.ClientResultException: HTTP 400 (invalid_request_error: unsupported_parameter)
Parameter: max_tokens
Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.
at Azure.AI.OpenAI.ClientPipelineExtensions.ProcessMessageAsync(ClientPipeline pipeline, PipelineMessage message, RequestOptions options)
at Azure.AI.OpenAI.Chat.AzureChatClient.CompleteChatAsync(BinaryContent content, RequestOptions options)
at OpenAI.Chat.ChatClient.CompleteChatAsync(IEnumerable`1 messages, ChatCompletionOptions options, CancellationToken cancellationToken)
Expected behavior
MaxOutputTokenCount  should set correct param based on the model
Actual behavior
Wrong param is set
Reproduction Steps
Call o1 model with setting MaxOutputTokenCount to a number
Environment
No response

Hi @dolphinsd ,
Thank you for raising this issue. Please hang tight while we take a look and do not hesitate to add more details if you have any.

Hi, confirmed, we've seen this also. Setting MaxOutputTokenCount=null works. Setting MaxOutputTokenCount to a number throws this error.
re-creatable code below:
        [Fact]
        public async Task AzureOpenAIChatCompletionShouldReturnExpectedResult()
        {
            // Arrange
            var azureClientOptions = new AzureOpenAIClientOptions(version: AzureOpenAIClientOptions.ServiceVersion.V2024_08_01_Preview);
            var client = new AzureOpenAIClient(new Uri("https://RESOURCE_NAME_HERE.openai.azure.com/"), new ApiKeyCredential(API_KEY_HERE), azureClientOptions);
            var chatCompletionsOptions = new ChatCompletionOptions()
            {
                MaxOutputTokenCount = 20000, // omit or set to null works
                Temperature = 1.0f
            };
            var messages = new List<ChatMessage>
            {
                new UserChatMessage("What's the Sun?")
            };

            // Act
            var chatClient = client.GetChatClient(o1-preview-2024-09-12-DEPLOYMENT_NAME_HERE);
            var response = await chatClient.CompleteChatAsync(messages, chatCompletionsOptions);
            var result = string.Concat(response.Value.Content.Select(c => c.Text));

            // Assert
            Assert.NotNull(result);
            CustomAssertions.ContainsEither(result, "sun", "Sun");
        }

The OpenAI.NET library has this working and routing through the MaxOutputTokenCount. Can this be fixed or applied with parity as this block o1 paramater settings.

authors: AngelosP bartczernicki dolphinsd janaka


text:
Storage: Make models implement IDisposable if they contain IDisposable properties

Especially BlobDownloadInfo and FileDownloadInfo where not disposing their Content stream can result in HttpClient not return the connection to the pool as quickly.

Duplicate of #7616


text:
Investigate: Improve the performance of success and error responses

Per Heath's comment: https://github.com/Azure/azure-sdk-for-net/pull/9080#discussion_r356843416

work with service team to document result sort order, if possible
reimplement merge algorithm

FYI @mssfang

Hopefully with the work on https://github.com/Azure/azure-sdk-for-net/issues/8704 we might be able to see if this is a concern or not

I believe that we are good for now. We have added performance tests. If we see a regression we will start looking here.
I will close this issue and will reopen when needed

authors: annelo-msft maririos


text:
Design document upload/merge/delete APIs

This tracks the work to design the APIs for the document upload/merge/delete APIs endpoint.
This includes:

Upload/merge/delete APIs

Fixed by #10568

authors: AlexGhiondea tg-msft


text:
[Event Hubs] Connection Idle Timeout Option

Summary
The focus of these changes is to allow the idle timeout applied to connections be specified as part of the options for each client.
References and Related

Expose additional idle timeout configuration in ConnectionOptions (#22674)

Fixes #22674

source: gharchive/pull-request


text:
feat(resourcemanager): add class reference type

add M4 property x-ms-mgmt-classReferenceType and its csharp attribute
add privatelink.json from common-types
tune privatelink and check name availability definitions

tune read-only so that they can match what are generated for RPs
rename some definitions

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

/azp run net - compute - ci

It has been decided that we will not add private endpoint classes into ResourceManager. Closing this issue.


text:
Diversify the test matrix

OS-TFM combinations were duplicated before.

Is this a result of your Debug/Release configuration change?

Is this a result of your Debug/Release configuration change?

No, Debug/Release configuration change didn't affect OS-TFM combinations.

Oh it looks like it is because of project vs package references. I don't like the fact that we have to explicitly list all the combinations as that is because it limits our sparse strategy across the matrix. @benbp are there other options? Could we maybe change the order of the parameters to mix this up a little better?

I chatted with @benbp and we came to a conclusion that this is the simplest option to get the coverage we need.

While I don't like the fact, we manually created this sparse matrix I will defer to @benbp Ben Broderick Phillips FTE to sign-off on this as the best approach.

@weshaggard this is another instance of the problem: "how do we traverse the matrix in a way that does not wrap (i.e. not diagonally)?" I remember last time we explored this problem in depth, it was not as simple as it seemed, because we can't generalize knowing which matrix dimensions to iterate vs. which not to, and exposing those knobs to the user is complicated at best while remaining deterministic.
It might be worth taking another look at it though and trying to come up with some form of solution, perhaps exploring more functionality around sub-matrices (walk a sparse matrix for parameters A and B, but walk through a subset of a full matrix for parameters C and D).

authors: benbp pakrym weshaggard


text:
Autorest Regen Preview to 3.0.0-alpha.20230912.3 by Rodge Fu from refs/pull/3677/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3677

API change check
API changes are not detected in this pull request.


text:
Autorest Regen Preview to 3.0.0-alpha.20231029.1 by Dapeng Zhang from refs/pull/3483/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3483

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.ChangeAnalysis


text:
Enable the new model serialization for service eabric

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

authors: azure-sdk mcgallan


text:
Translating legacy SdkDirectory param to SdkRootDirectory

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Approved by @shahabhijeet


text:
Codespaces onboarding for Python repository

This is a tracking issue for anything that comes up when folks start dogfooding Codespaces against the repository. As folks discover tools/configuration that they'd like to have pre-installed by default note it here and we can submit PRs that put it there by default.

Doesn't appear to be anymore feedback.

Doesn't appear to be anymore feedback.

repo: Azure/azure-sdk-for-python


text:
azure-mgmt-loganalytics: LICENSE missing in PyPi

Package Name:  azure-mgmt-loganalytics
Package Version: 11.0.0
Operating System: Linux
Python Version: 3.9.6

Describe the bug
The LICENSE file is missing from the azure-mgmt-loganalytics package in PyPi.
Additional context
I am making a PR to fix this now.

@major, thanks for the feedback and future contribution (again)! Directing it to the right people, so they know!

same issue : https://github.com/Azure/azure-sdk-for-python/issues/20183

authors: major msyyc swathipil


text:
azure-ai-ml inconsistently installing -> causing random build failures in dependent packages

This first was noticed by @pvaneck working on #33282 he created a totally standalone pr here #33838 which also adds the removed anyio dependency to azure-ai-resources dev_requirement.
That apparently worked, though reading the build logs it makes no sense why it would.
Details that I've been able to sus out so far while looking at the build failures and more recently a windows failure.

CI replaces all relative dev_req paths with prebuilt wheels at runtime. This allows multiple tox envs to run at the same time without accidentally stomping on each other while assembling a wheel for usage.
CI successfully installs dev_reqs, which should satisfy the requirement for azure-ai-ml, but "sometimes doesn't" as is shown in the first build failure.

Need to run a couple investigatory builds to understand the failure.

Resolved by #33908

6


text:
Resolve Checkout of AutoRest repo during verify-autorest

Still on master.

Overriding due to the fact that this is a safe change.

/check-enforcer override


text:
SB tests to env loader

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run python - servicebus - tests

/azp run python - servicebus - tests

API changes have been detected in azure-servicebus. You can review API changes here
API changes
-             filter: Union[CorrelationRuleFilter, SqlRuleFilter] = <azure.servicebus.management._models.TrueRuleFilter object at 0x00000248711C3070>,
+             filter: Union[CorrelationRuleFilter, SqlRuleFilter] = <azure.servicebus.management._models.TrueRuleFilter object at 0x000002A4BF183070>,
-             filter: Union[CorrelationRuleFilter, SqlRuleFilter] = <azure.servicebus.management._models.TrueRuleFilter object at 0x0000024870CA1D80>,
+             filter: Union[CorrelationRuleFilter, SqlRuleFilter] = <azure.servicebus.management._models.TrueRuleFilter object at 0x000002A4BEC61D80>,

/azp run python - servicebus - ci

API change check for azure-servicebus
API changes have been detected in azure-servicebus. You can review API changes here
API changes
-             filter: Optional[Union[CorrelationRuleFilter, SqlRuleFilter]] = <azure.servicebus.management._models.TrueRuleFilter object at 0x000001D7B5457220>,
+             filter: Optional[Union[CorrelationRuleFilter, SqlRuleFilter]] = <azure.servicebus.management._models.TrueRuleFilter object at 0x0000014B48E87220>,
-             filter: Optional[Union[CorrelationRuleFilter, SqlRuleFilter]] = <azure.servicebus.management._models.TrueRuleFilter object at 0x000001D7B4F25540>,
+             filter: Optional[Union[CorrelationRuleFilter, SqlRuleFilter]] = <azure.servicebus.management._models.TrueRuleFilter object at 0x0000014B48959540>,

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/reopen


text:
[AutoPR network/resource-manager] Swagger changes

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3857

Codecov Report

Merging #3313 into restapi_auto_Network-September-Release will decrease coverage by 3.58%.
The diff coverage is n/a.

@@                            Coverage Diff                             @@
##           restapi_auto_Network-September-Release    #3313      +/-   ##
==========================================================================
- Coverage                                   55.31%   51.73%   -3.59%
==========================================================================
  Files                                        9459     5884    -3575
  Lines                                      189228   152063   -37165
==========================================================================
- Hits                                       104680    78667   -26013
+ Misses                                      84548    73396   -11152

Impacted Files
Coverage Δ

...ure/mgmt/recoveryservicesbackup/models/__init__.py
51.91% <0%> (-48.09%)
:arrow_down:

azure-batch/azure/batch/models/__init__.py
52.15% <0%> (-47.85%)
:arrow_down:

...ights/azure/applicationinsights/models/__init__.py
53% <0%> (-47%)
:arrow_down:

...ure-mgmt-media/azure/mgmt/media/models/__init__.py
53.33% <0%> (-46.67%)
:arrow_down:

.../azure/mgmt/compute/v2018_06_01/models/__init__.py
53.35% <0%> (-46.65%)
:arrow_down:

.../azure/mgmt/compute/v2018_04_01/models/__init__.py
53.35% <0%> (-46.65%)
:arrow_down:

...iveservices/search/entitysearch/models/__init__.py
53.75% <0%> (-46.25%)
:arrow_down:

azure-eventgrid/azure/eventgrid/models/__init__.py
53.75% <0%> (-46.25%)
:arrow_down:

...ration/azure/mgmt/datamigration/models/__init__.py
53.89% <0%> (-46.11%)
:arrow_down:

...mgmt-monitor/azure/mgmt/monitor/models/__init__.py
54.1% <0%> (-45.9%)
:arrow_down:

... and 3679 more

Continue to review full report at Codecov.

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

authors: AutorestCI codecov-io


text:
Skip yml files for which parsing failed

Skip checking yml file if it parsing fails.
For https://github.com/Azure/azure-sdk-tools/issues/3540#event-6920318338

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow

authors: azure-sdk chidozieononiwu

repo: Azure/azure-sdk-tools


text:
Remove directory climbing for assets.json

Remove directory climbing for assets.json. The path to the assets.json is either the full path to the assets.json file or it is the directory in which the assets.json file exists. Don't climb the directory looking for it.
In GitStore.cs renamed FileName, which is the name of the assets.json file, to AssetsJsonFileName to more clearly define what it refers to.
Also added a test case for #4339, which adds --tags to git fetch.
Fixes #3960

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests


text:
Update stress workbook parameters to filter by time->namespace->pod

This change reduces pod name noise in the dropdown, as we now filter by namespace first, and then also group the pod names by date. Additionally, the query time range for namespace/pods is configurable, so it's possible to look up non-active pods in the dashboard now.

Pod query diff:
3,4c3,5
< | distinct InstanceName
< | extend ResourceId = split(InstanceName, \'/\')
---
> | extend DayBin = bin(TimeGenerated, 3d)
> | summarize arg_max(TimeGenerated, *) by InstanceName
> | extend ResourceId = split(InstanceName, "/")
7d7
< | distinct ContainerName, PodUid
12c12
<   | where Namespace != "kube-system" and Namespace != "stress-infra"
---
>   | where Namespace in ({NamespaceParameter})
15c15,17
< | project value = PodUid, label = Name, group = Namespace
---
> | extend day = tostring(format_datetime(DayBin, "MM/dd"))
> | sort by day desc
> | project value = PodUid, label = Name, group = day

and do we not want the kube-system and stress-infra namespaces to be excluded anymore? can we get valuable info from those

and do we not want the kube-system and stress-infra namespaces to be excluded anymore? can we get valuable info from those

@ckairen They are effectively excluded still because you now choose a namespace and we filter against that. The new namespace dropdown parameter does exclude kube-system (query below), but I don't exclude stress-infra because it could be nice to view our service stats from this dashboard.
KubePodInventory\r\n| distinct Namespace\r\n| where Namespace !in ("kube-system", "kubernetes-dashboard", "gatekeeper-system")

authors: benbp ckairen


text:
Change appropriate "preview" references to "beta"

Bookmarks and any reference to service preview versions were not changed.

I wasn't sure whether to change a script in there for Java, so I added a TODO. Should a doc or blurb be added as to why we decided to change?

Closing in favor of https://github.com/Azure/azure-sdk/pull/1536. I believe I have captured everything you have here in my PR but please let me know if I missed something.

authors: heaths weshaggard

repo: Azure/azure-sdk


text:
[Python Packages] update csv

https://github.com/Azure/azure-sdk-for-python/issues/23831

@czubair Could you help confirm if these comply with our naming pattern?


text:
[ArgumentNullException: Value cannot be null. Parameter name: username]

I'm getting an ArgumentNullException in SignalR negotiate,

Request URL: http://localhost:1623/signalr/negotiate?clientProtocol=2.1&connectionData=[{"name"%3A"notificationshub"}]&_=1566915910789
Request Method: GET
Status Code: 500 Internal Server Error

It seems it has something to do with the claims I'm currently using in my project, I've tried setting a claimsprovider at initialization as the Troubleshooting Guide states:
services.MapAzureSignalR(GetType().FullName, options =>
            {
                // pick up necessary claims
                options.ClaimsProvider = (context) => context.Authentication?.User.Claims.Where(...);
            });

and filtering out all my claims, but the error persist.
here is the Callstack:

System.Web.Util.SecUtility.CheckParameter(String& param, Boolean checkForNull, Boolean checkIfEmpty, Boolean checkForCommas, Int32 maxSize, String paramName) +161
System.Web.Security.SqlRoleProvider.GetRolesForUser(String username) +59
WebMatrix.WebData.SimpleRoleProvider.GetRolesForUser(String username) +54
System.Web.Security.RolePrincipal.GetRoles() +208
System.Web.Security.<get_Claims>d__4.MoveNext() +65
System.Security.Claims.<get_Claims>d__51.MoveNext() +247
System.Security.Claims.<get_Claims>d__37.MoveNext() +212
Microsoft.Azure.SignalR.d__6.MoveNext() +1060
Microsoft.Azure.SignalR.AspNet.d__13.MoveNext() +372
System.Linq.d__591.MoveNext() +193    System.Security.Claims.ClaimsIdentity.SafeAddClaims(IEnumerable1 claims) +101
System.Security.Claims.ClaimsIdentity..ctor(IIdentity identity, IEnumerable1 claims, String authenticationType, String nameType, String roleType, Boolean checkAuthType) +12675858    Microsoft.Azure.SignalR.AuthenticationHelper.GenerateJwtBearer(String issuer, String audience, IEnumerable1 claims, Nullable1 expires, String signingKey, String requestId) +185    Microsoft.Azure.SignalR.AuthenticationHelper.GenerateAccessToken(String signingKey, String audience, IEnumerable1 claims, TimeSpan lifetime, String requestId) +122
Microsoft.Azure.SignalR.AspNet.ServiceEndpointProvider.GenerateClientAccessToken(String hubName, IEnumerable1 claims, Nullable1 lifetime, String requestId) +116
Microsoft.Azure.SignalR.AspNet.NegotiateMiddleware.ProcessNegotiationRequest(IOwinContext owinContext, HostContext context) +596
Microsoft.Azure.SignalR.AspNet.NegotiateMiddleware.Invoke(IOwinContext owinContext) +67
Microsoft.Owin.Infrastructure.OwinMiddlewareTransition.Invoke(IDictionary`2 environment) +46
Microsoft.Owin.Mapping.d__0.MoveNext() +273
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__5.MoveNext() +182
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Security.Infrastructure.d__0.MoveNext() +638
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Security.Infrastructure.d__0.MoveNext() +638
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Security.Infrastructure.d__0.MoveNext() +638
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Security.Infrastructure.d__0.MoveNext() +638
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__5.MoveNext() +182
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +102
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +64
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.d__2.MoveNext() +180
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.StageAsyncResult.End(IAsyncResult ar) +69
Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult ar) +64
System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +483
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +132
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +163

The callstack shows that ArgumentNullException throws from WebMatrix.WebData.SimpleRoleProvider.GetRolesForUser.
When enumerating User.Claims to generate the jwt token, GetRoles is called however the SimpleRoleProvider throws. I wonder if this is similar to the one described here: http://www.lhotka.net/weblog/CallingRolesGetRolesForUserInAWCFService.aspx
To prevent the issue from blocking negotiate, you can try the following:
services.MapAzureSignalR(GetType().FullName, options =>
            {
                // specify the claim instead enumerate User.Claims
                options.ClaimsProvider = (context) => new Claim[]
                    {
                    new Claim("customClaim1", "value"),
                    };
            });

I did try to set an empty list in ClaimsProvider to see if that was the case, but I still get the error.

How you set an empty list? And what is the callstack of the error when you set an empty list?

@vicancy You where right, I was setting an empty list but using context.Authentication?.User.Claims.Where(...) with a where clause that didn't return anything, I guess that line was the responsible of making the call to WebMatrix.WebData.SimpleRoleProvider.GetRolesForUser.
I changed it to new Claim[] as you suggested and it worked.
Thanks for your help

repo: Azure/azure-signalr


text:
[Module Proposal]: API Management Service

Have you checked this module does not already exist in the registry?
Yes
Why is the module needed?
There is no existing module available in the public registry, but is common deployed by customers developing their own APIs.
Module path
apim/service
Describe the module
Deploy APIM service in a VNET with a global policy including basic CORS with options:

Custom domains
Managed Identities
Azure AD Developer Portal identities

Dear @BernieWhite , Azure Verified Modules (AVM) will become the single Microsoft standard for Bicep modules. Transitioning to AVM, module proposals for new, non-AVM modules will no longer be accepted and we encourage you to propose a new AVM module, which you can file here: Module Proposal, here.
See this informational notice for more details on the upcoming changes.
Thank you for your understanding!

authors: BernieWhite ChrisSidebotham

repo: Azure/bicep-registry-modules


text:
Type checking is not working for intermediate variables

Repro here:
resource vmWorking 'Microsoft.Compute/virtualMachines@2020-06-01' = {
  name: 'working'
  location: 'west us'
  properties: {
    // diagnostics raised - we have a property that doesn't make sense.
    valThatDoesNotExist: ''
  }
}

var vmNotWorkingProps = {
  valThatDoesNotExist: ''
}

resource vmNotWorking 'Microsoft.Compute/virtualMachines@2020-06-01' = {
  name: 'working'
  location: 'west us'
  // no diagnostics raised here even though the type is invalid!
  properties: vmNotWorkingProps
}

Yeah, that's a bad bug. Definitely need to fix that in 0.2.

Did some digging on this; it's actually not going to be that simple to fix. In type validation we check for various syntaxes to recurse over: https://github.com/Azure/bicep/blob/2c5fa92129305e0e0b9a90b053bbc8fc91fff9a8/src/Bicep.Core/TypeSystem/TypeValidator.cs#L168
We need to ensure we recurse over VariableAccessSyntax, but need to be careful to attach diagnostics to the reference to the variable reference, rather than the variable value itself.

We should make sure when we fix this that for the following:
var varWithLiterals = [
  {
    prop: 'ValA'
  }
  {
    prop: 'ValB'
  }
]

Our type system should be able to infer the type of:
varWithLiterals[someIndex].prop

as 'ValA' | 'ValB' (union of string literals) rather than just string.

I'm planning to discuss this with the team today - we have some decisions to make about what the errors will look like.

authors: anthony-c-martin majastrz

repo: Azure/bicep


text:
SystemAssigned Identity being created when creating UserAssigned

Bicep version
Bicep CLI version 0.11.1 (030248df55)
Describe the bug
When creating ONLY a UserAssigned identity on a Microsoft.Compute/virtualMachines resource, a SystemAssigned identity is created too. This means when the deployment finishes both a System and User identity are present.
We see this in the ARM (taken from export template in the portal)
To Reproduce
resource vm 'Microsoft.Compute/virtualMachines@2022-08-01' = {
  name: vmName
  location: location
  tags: tags
  identity: {
    type: 'UserAssigned'
    userAssignedIdentities: {
      '${identities}': {}
....

The deployment is successful, but the ARM from the portal shows:
"resources": [
        {
            "type": "Microsoft.Compute/virtualMachines",
            "apiVersion": "2022-03-01",
            "name": "[parameters('virtualMachines_vm01')]",
            "location": "uksouth",
            "tags": {
                "Environment": "Demo",
                "Owner": "user@domain.co.uk",
                "Service": "Product",
                "Deployment Date": "2022-10-24"
            },
            "identity": {
                "type": "SystemAssigned, UserAssigned",
                "userAssignedIdentities": {
                    "/subscriptions/ID/resourceGroups/RGNAME/providers/Microsoft.ManagedIdentity/userAssignedIdentities/msi-vm01": {}
                }
            },

This does not look like a bicep specific issue. We would recommend you instead open up a support ticket so this can be routed to the compute/virtualMachines team.

authors: alex-frankel cmptscpeacock


text:
Error BCP037: The property "frontEndIpConfigurationName" is not allowed on objects of type "params". No other properties are allowed.

Bicep version
Bicep CLI version 0.11.1 **(030248df55)**
Describe the bug
I moved my load balancer resource into a module, and exposed a parameter for the front end ip config name:
@description('name of the front end ip configuration that is created for the ip address.')
param frontEndIpConfigurationName string

resource loadBalancer 'Microsoft.Network/loadBalancers@2022-05-01' = {
  name: name
  location: location
  properties: {
    frontendIPConfigurations: [
      {
        name: frontEndIpConfigurationName

In main.bicep I included this module and set this param

var outboundRuleName = 'rule-${stackName}-${envMap[environmentType].shortName}-${shortLocationName}-01'
var frontEndIpConfigurationName = 'ipConfig1'
module loadBalancer 'modules/load-balancer.bicep' = {
  name: 'loadBalancer'
  params: {
    name: loadBalancerName
    location: location
    publicIpAddressId: loadBalancerPublicIp.outputs.ipAddressId
    backendAddressPoolName: swarmClusterBackendAddressPoolName
    frontEndIpConfigurationName: frontEndIpConfigurationName

No editor warnings or errors at this point.
Proceeded to deploy - resulted in an error
Error BCP037: The property "frontEndIpConfigurationName" is not allowed on objects of type "params". No other properties are allowed.

Renaming the parameter from frontEndIpConfigurationName to something else solves the problem.
It seemed to me like this parameter name has some kind of special treatment in bicep.
To Reproduce
As per above
Additional context

Could you provide the full template for main.bicep and modules/load-balancer.bicep?
I tried to create a minimal reproduction but didn't run into any errors with the following templates:
main.bicep
module mod 'mod.bicep' = {
  name: 'mod'
  params: {
    frontEndIpConfigurationName: 'frontEndIpConfigurationName'
  }
}

mod.bicep
param frontEndIpConfigurationName string

The BCP037 error posted would be raised when the module has no parameter named "frontEndIpConfigurationName" and no parameters remained unspecified. Had modules/load-balancer.bicep been saved with the new parameter when you ran into the error?

@jeskew i've updated to latest bicep version since it happened, and I can no longer reproduce. I would like to think I had checked the file was saved, however perhaps there was an issue. Happy to close for now, will reopen if it crops up again.

authors: dazinator jeskew


text:
AzureDeployment Environment Dev center setup failing with key vault Integration

I was trying to create a Azuredeployment environment and Dev center with in it. When I am trying to create a catalog within the Devcenter using the keyvault integration (with private endpoint enabled), the catalog creation is failing.

We couldn't connect to ade-zzzzzzz. The DevCenter is misconfigured. Inform DevCenter owners that the key vault could not be found, and is required for this operation.

We already created a system managed identity for the devcenter and add thed the system managed identity to full permission for the secret in the keyvault. But still the catalog creation is failing. So a private keyvault is not supported with AzureDeployment environment?

Hi @vivuu1989, that is correct. Private endpoint is currently unsupported. This feature is in our backlog, but there is not currently a timeline on when it will become available.

Hi @vivuu1989, that is correct. Private endpoint is currently unsupported. This feature is in our backlog, but there is not currently a timeline on when it will become available.

is there any workaround to overcome this blocker?

repo: Azure/deployment-environments


text:
show underlying docker/helm commands on request

Currently, there is a lot of black magic that goes on when draft up is run, spanning at least docker and helm commands.
$ draft up --debug
Draft Up Started: 'my-service': 01CFDW1HQQ5B3ZCGP3YZHFYFPK
my-service: Building Docker Image: SUCCESS ⚓  (1.0038s)
my-service: Pushing Docker Image: SUCCESS ⚓  (2.2107s)
my-service: Releasing Application: FAIL ❌  (1.3373s)
Inspect the logs with `draft logs 01CFDW1HQQ5B3ZCGP3YZHFYFPK`
[debug] No post deploy tasks to run

However, with this issue that is happening on releasing the application, the logs do show a yaml rendering error, but it is relatively hard to debug what might be going on. I believe it would be good if there could be an option to show what helm commands are being run under the hood, so that advanced users can tweak the commands/parameters to assist in the debugging process (for example, by adding --debug or --dry-run flags - although for YAML rendering errors specifically that may not help as much).
I could see something similar for docker commands, but those are relatively less problematic in general, so that could be out of scope for this.
as demonstrated above, passing --debug to the draft up command, which according to the documents might be a reasonable guess to activate this functionality, barely adds any additional information.

docker variant of this could be a workaround for #806 if it enables the underlying docker commands that user can run manually :)

repo: Azure/draft


text:
Question: Summary of changes to be used in PR comments

Not a bug but a feature request / question
Is there a way to create a summary of the changes about to happen which could be used in PR comments? When creating the PR we can use the tenant plan workflow to review what is going to happen but it requires a few extra steps. What would be nice to have some kind of sanitized summary of the changes and assignments which we could use to create a PR comment with a workflow.

There is a global variable called epacInfoStream which all output is appended to, including the summary of changes. I've used this output in the body of a PR

Oh nice one @anwather ! That would work but seems to require a bit of cleanup to be used in a PR comment

authors: anwather teemukom

repo: Azure/enterprise-azure-policy-as-code


text:
UUID deprication warning

Package Name:
@azure/ms-rest-js
Package Version:
Operating system:
[x] nodejs

version:

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
UUID version 3 is deprecated. version 7 is the minimum version. Please update the UUID version of this project. Right now I'm getting the following errors when doing a clean install.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

it is caused by the following import
"@azure/ms-rest-js": {
      "version": "2.1.0",
      "resolved": "https://registry.npmjs.org/@azure/ms-rest-js/-/ms-rest-js-2.1.0.tgz",
      "integrity": "sha512-4BXLVImYRt+jcUmEJ5LUWglI8RBNVQndY6IcyvQ4U8O4kIXdmlRz3cJdA/RpXf5rKT38KOoTO2T6Z1f6Z1HDBg==",
      "requires": {
        "@types/node-fetch": "^2.3.7",
        "@types/tunnel": "0.0.1",
        "abort-controller": "^3.0.0",
        "form-data": "^2.5.0",
        "node-fetch": "^2.6.0",
        "tough-cookie": "^3.0.1",
        "tslib": "^1.10.0",
        "tunnel": "0.0.6",
        "uuid": "^3.3.2",
        "xml2js": "^0.4.19"
      },
      "dependencies": {
        "uuid": {
          "version": "3.4.0",
          "resolved": "https://registry.npmjs.org/uuid/-/uuid-3.4.0.tgz",
          "integrity": "sha512-HjSDRw6gZE5JMggctHBcjVak08+KEVhSIiDzFnT9S9aegmp85S/bReBVTb4QTFaRNptJ9kuYaNhnbNEOkbKb/A=="
        }
      }

To Reproduce
Steps to reproduce the behavior:

install project with npm ci

Expected behavior
a clean install without deprication warnings

@ramya-rao-a
The import comes from @azure/storage-blob. I've pasted the import from package.json. The snippet above is from package-lock.json.
"@azure/storage-blob": "^10.5.0"

in package-lock.json, I've got the following import of ms-rest-js.
"node_modules/@azure/storage-blob": {
      "version": "10.5.0",
      "resolved": "https://registry.npmjs.org/@azure/storage-blob/-/storage-blob-10.5.0.tgz",
      "integrity": "sha512-67+0EP7STy9BQgzvN1RgmSvXhxRd044eDgepX7zBp7XslBxz8YGo2cSLm9w5o5Qf1FLCRlwuziRMikaPCLMpVw==",
      "dependencies": {
        "@azure/ms-rest-js": "^2.0.0",
        "events": "^3.0.0",
        "tslib": "^1.9.3"
      }
    }

@ramya-rao-a
I thought I was using the latest version of @azure/storage-blob. But I wasn't. I've updated to the latest version v12 and there are no errors from the azure SDK anymore. MSSQL still has an import of an out-of-date tedious package. And I'm using the latest version from them.
But that issue does not fit in the context of the azure-sdk. Thanks for the help.

Thanks for getting back to us on that @AlexSpelt !
While we have you here, can you share if there were any documentation that led you to using v10 of @azure/storage-blob? We would like to make sure such documentation gets updated.

I think I developed the azure storage implementation about 1 to 2 years ago. It has nothing to do with the documentation. I thought npm install updated packages. It only does that in a minor way.
But marking version 10 and all other versions that use deprecated packages, as deprecated, would have helped me find the root of the problem more quickly.

Thanks for the feedback @AlexSpelt

authors: AlexSpelt ramya-rao-a

repo: Azure/ms-rest-js


text:
akv-plugin .NET version is required

Go doesn't support PKCS12 certificate well, so we need a .NET version plugin to fix the PKCS12 issue.

The major work of .NET version has been done, so I will close the issue.

repo: Azure/notation-azure-kv


text:
SecretObject not found; volume gets mounted

Have you

[y] Read Troubleshooting Guide
[y ] Searched on GitHub issues and Discussions

SecretProvider.yaml

Deployment.yaml

kubectl describe pd

@rucheeg Thank you for reporting the issue.
The logs from secrets-store container in the driver pod should have more information on why the sync secret failed. Here is our troubleshooting guide: https://azure.github.io/secrets-store-csi-driver-provider-azure/troubleshooting/
Did you set secrets-store-csi-driver.syncSecret.enabled=true as part of helm install while setting up the driver and provider? As of the last release, the RBAC roles and rolebindings required for sync secret are not installed by default. They need to be explicitly set as part of helm install command.
Here is a list of helm configurable values: https://github.com/Azure/secrets-store-csi-driver-provider-azure/tree/master/charts/csi-secrets-store-provider-azure#configuration
Release notes: https://azure.github.io/secrets-store-csi-driver-provider-azure/upgrading/#upgrading-to-helm-chart-version-0020

Thanks for your quick response @aramase. The only error I see is following in driver logs. There are no errors in provider logs.
E0615 16:39:48.653579       1 reflector.go:138] pkg/mod/k8s.io/client-go@v0.20.2/tools/cache/reflector.go:167: Failed to watch *v1.Secret: failed to list *v1.Secret: secrets is forbidden: User "system:serviceaccount:cluster-addons:secrets-store-csi-driver" cannot list resource "secrets" in API group "" at the cluster scope
I've asked the team that installed the driver/provider if they enabled the syncSecret.

@rucheeg Yeah, that looks like the issue with the syncSecret not enabled.
I'm adding this step to few other docs and our troubleshooting guide:  https://github.com/Azure/secrets-store-csi-driver-provider-azure/pull/543.

Thanks @aramase! you were spot on. That fixed the error. Appreciate the quick turnaround!

authors: aramase rucheeg


text:
Node module caching

Morning team. Firstly thanks for all your work on this, really appreciating the fixes. I do have a question about caching node modules. I've been using the cache@v2 action for caching ./node_modules using the lockfile as a key in my non-SWA based repos but it doesn't work here as it doesn't appear that the swa action copies node_modules into the Oryx workspace. As a result the npm dependencies have to be downloaded again.
I did wonder about copying them into the Oryx working dir using a custom build command but 1. that seems like a bit of a hack and 2. I'm not even sure that would work for projects with separate frontend and api lockfiles?
Is this a viable way of doing it or have I missed something?

@kichalla are there any plans to add the ability to Oryx to pull node modules from a GH action cache?

Are there any updates on this? Our build takes 3 minutes to pull all node modules, costing both time and unneccessary npm bandwidth i guess.

authors: Strepto henryjcee miwebst

repo: Azure/static-web-apps


text:
Use private_endpoint_network_policies_enabled instead of enforce_private_link_endpoint_network_policies in the example code

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Now the azurerm_subnet resource in the example folder used enforce_private_link_endpoint_network_policies:
resource "azurerm_subnet" "test" {
  address_prefixes                               = ["10.52.0.0/24"]
  name                                           = "${random_id.prefix.hex}-sn"
  resource_group_name                            = local.resource_group.name
  virtual_network_name                           = azurerm_virtual_network.test.name
  enforce_private_link_endpoint_network_policies = true
}

The enforce_private_link_endpoint_network_policies has been deprecated and will be removed in azurerm 4.0, we should use private_endpoint_network_policies_enabled instead.
New or Affected Resource(s)/Data Source(s)
azurerm_subnet
Potential Terraform Configuration
resource "azurerm_subnet" "test" {
  address_prefixes                          = ["10.52.0.0/24"]
  name                                      = "${random_id.prefix.hex}-sn"
  resource_group_name                       = local.resource_group.name
  virtual_network_name                      = azurerm_virtual_network.test.name
  private_endpoint_network_policies_enabled = true
}

References
https://github.com/hashicorp/terraform-provider-azurerm/blob/main/internal/services/network/subnet_resource.go#L207

I am also getting the exact same error. Any update on this?

Hi @ravick4u I've tried a fix but I found that we cannot use private_endpoint_network_policies_enabled directly now as this response pointed out.

Anyone coming here after googling this error:
Error: Unsupported argument
│
│   on ./path/to/virtual_network/subnets.tf line 8, in resource "azurerm_subnet" "additional_subnets":
│    8:   private_endpoint_network_policies_enabled = each.value.enable_pe_policy

Hashicorp released AzureRM v4.0.0 11 hours ago, which apparently breaks the suggested fix as well.

authors: BenjaminNolan lonegunmanb ravick4u

repo: Azure/terraform-azurerm-aks


text:
Make the Azure Key Vault public because private Key Vault requires preview API

Running Microsoft Terraform module AKS end to end tests I get this new error message I have never seen before from the ARM API:
https://github.com/Azure/terraform-azurerm-aks/actions/runs/11665268834/job/32477571013?pr=598#step:3:6605
HTTP 400 "Vnet integration should be enabled when KeyVault network access is Private."
I believe this is the root cause:
https://learn.microsoft.com/en-us/azure/aks/use-kms-etcd-encryption#prerequisites ( See yellow warning box)
However Vnet Integration is still preview as far as I know. Terraform provider azurerm V4 will not support preview features. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#aks-migration-to-stable-api
This is a workaround to get the CI running again.
This PR needs to be reverted once AKS API Vnet Integration goes GA

The end to end test is now failing on the upgrade step. It cannot pass the upgrade test because the current main branch cannot pass the end to end test.


text:
Module outputs refer to sensitive values

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: 1.5.7 (latest shipped for MacOS with homebrew)
azure provider: >= 3.74.0
module: 5.0.3
Description
Describe the bug
I'm deploying a testing version of the landing zone, with demo landing zones, and identity, management, and connectivity resources enabled, without any additional configuration.
Running terraform plan results in the following error:
Error: Output refers to sensitive values
│
│   on outputs.tf line 84:
│   84: output "azurerm_log_analytics_workspace" {
│
│ To reduce the risk of accidentally exporting sensitive data that was
│ intended to be only internal, Terraform requires that any root module
│ output containing sensitive data be explicitly marked as sensitive, to
│ confirm your intent.
│
│ If you do intend to export this data, annotate the output value as
│ sensitive by adding the following argument:
│     sensitive = true

and a similar one on line 102.
Steps to Reproduce

Configure the module as follows:

module "enterprise_scale" {
  source  = "Azure/caf-enterprise-scale/azurerm"
  version = "5.0.3" # change this to your desired version, https://www.terraform.io/language/expressions/version-constraints

  default_location = var.location
  default_tags     = var.tags

  providers = {
    azurerm              = azurerm
    azurerm.connectivity = azurerm
    azurerm.management   = azurerm
  }

  root_parent_id = data.azurerm_client_config.core.tenant_id
  root_id        = var.root_id
  root_name      = var.root_name

  deploy_demo_landing_zones = true

  deploy_management_resources = true
  subscription_id_management  = module.subscriptions.subscription_id_map[local.subscription_name_management]

  deploy_identity_resources = true
  subscription_id_identity  = module.subscriptions.subscription_id_map[local.subscription_name_identity]

  deploy_connectivity_resources = true
  subscription_id_connectivity  = module.subscriptions.subscription_id_map[local.subscription_name_connectivity]
}

run terraform plan

Proposed solution

Add the sensitive = true argument to the above-mentioned outputs on lines 84 and 102 in outputs.tf (I'm currently using this as a fix on my fork of the repository)
Since the outputs are considered sensitive, consider removing said outputs

I'm willing to submit a pull request once the solution has been decided.

Hey @JaegerP I just tested your solution locally and it seems to work.

Hi can you please confirm terraform versions, provider versions and module version.
Can you please also supply module config?
Thanks!

Hi - apologies we will try and repro this. Can you confirm the exact provider version that you are experiencing the issue with?

Hi @matt-FFFFFF, I've tried several provider versions, since I first assumed it might be an issue with 3.89, but the problem persisted with 3.88, and all the way back to 3.74.

@matt-FFFFFF any update on this?

@JaegerP I created the pull request to fix this.

Thanks @Laudenlaruto. Any estimate when the fix will be included in a release?

authors: JaegerP Laudenlaruto matt-FFFFFF


text:
Support JsonWebKeys with the Elliptic Curve key type

Refactored JsonWebKeySet.GetSigningKeys() method and added support for JWKs with 'kty' = 'EC'.
Refactored OpenIdConnect E2E tests (Fact -> Theory).
Added E2E OpenIdConnect tests where jwks metadata contains EC JWKs with P-256, P-384, and P-521 curves.
Added test where EC JWKs obtained from the metadata is not valid (unsupported curve).
Added test where a token is signed using a key which is not part of the metadata.

Would love to see this merged in, more and more services are generating ECD keys.

Closing this pull request in favor of #1143
Reason: Too many conflicts. We want this change in 5.5.0 and this PR is based on our dev branch.

authors: GeoK SaltyDH


text:
Can't Sign in again  after cancelling the authentication popup by the close or back button

Core Library
MSAL Node (@azure/msal-node)
Core Library Version
1.9.0
Wrapper Library
MSAL Node Extensions (@azure/msal-node-extensions)
Wrapper Library Version
1.9.0
Description
Hi Team, thank you for your efforts and your support I have a critical issue that I can't sign in again  to my account after canceling the authentication popup by the close button or back button

Error Message
I can't log in again after canceling and trying to authenticate again, I should close the second one and try again and it will authenticate successfully, the login stopped like the attached photo I think that the  authProvider.login() function doesn't call anywhere
it gives me an error message:'Object has been destroyed' when I click the close button but this message appears when I try login again not after the close popup
it gives me an error message:'No code found in URL' when I click the click button

Msal Logs
No response
MSAL Configuration
const MSAL_CONFIG = {
	auth: {
		clientId: "XXXXX-XXX-XXXXXXX",
		authority: `https://login.microsoftonline.com/common/`,
	},
	// cache: {
	// 	cachePlugin
	// },
	system: {
		loggerOptions: {
			loggerCallback(loglevel, message, containsPii) {
				console.log(message);
			},
			piiLoggingEnabled: false,
			logLevel: LogLevel.Verbose,
		}
	}
};

Relevant Code Snippets
class AuthProvider {

	clientApplication;
	cryptoProvider;
	authCodeUrlParams;
	authCodeRequest;
	pkceCodes;
	account;

	constructor() {
		/**
		 * Initialize a public client application. For more information, visit:
		 * https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-node/docs/initialize-public-client-application.md
		 */
		this.clientApplication = new PublicClientApplication(MSAL_CONFIG);
		this.account = null;

		// Initialize CryptoProvider instance
		this.cryptoProvider = new CryptoProvider();

		this.setRequestObjects();
	}

	/**
	 * Initialize request objects used by this AuthModule.
	 */
	setRequestObjects() {
		const requestScopes = [
			'openid',
			'profile',
			'User.Read'
		];
		const redirectUri = "msal://redirect";

		this.authCodeUrlParams = {
			scopes: requestScopes,
			redirectUri: redirectUri
		};

		this.authCodeRequest = {
			scopes: requestScopes,
			redirectUri: redirectUri,
			code: null
		}

		this.pkceCodes = {
			challengeMethod: "S256", // Use SHA256 Algorithm S256 RS256
			verifier: "", // Generate a code verifier for the Auth Code Request first
			challenge: "" // Generate a code challenge from the previously generated code verifier
		};
	}
	static createAuthWindow() {
		return new BrowserWindow({
			width: 400,
			height: 600
		});
	}
	async login() {
		const authResult = await this.getTokenInteractive(this.authCodeUrlParams);
		this.handleResponse(authResult);
		return authResult;
	}

	async logout() {
		if (this.account) {
			await this.clientApplication.getTokenCache().removeAccount(this.account);
			this.clientApplication.clearCache();
			this.account = null;
		}
	}
	async getToken(request) {
		let authResponse;
		const account = this.account || await this.getAccount();
		if (account) {
			request.account = account;
			authResponse = await this.getTokenSilent(request);
		} else {
			const authCodeRequest = { ...this.authCodeUrlParams, ...request };
			authResponse = await this.getTokenInteractive(authCodeRequest);
		}

		return authResponse.accessToken || null;
	}
	async getTokenInteractive(tokenRequest) {
		// Generate PKCE Challenge and Verifier before request
		const cryptoProvider = new CryptoProvider();
		const { challenge, verifier } = await cryptoProvider.generatePkceCodes();
		const authWindow = AuthProvider.createAuthWindow();

		// Add PKCE params to Auth Code URL request
		const authCodeUrlParams = {
			...this.authCodeUrlParams,
			scopes: tokenRequest.scopes,
			codeChallenge: challenge,
			codeChallengeMethod: "S256"
		};

		try {
			// Get Auth Code URL
			const authCodeUrl = await this.clientApplication.getAuthCodeUrl(authCodeUrlParams);

			const authCode = await this.listenForAuthCode(authCodeUrl, authWindow);

			// Use Authorization Code and PKCE Code verifier to make token request
			const authResult = await this.clientApplication.acquireTokenByCode({
				...this.authCodeRequest,
				code: authCode,
				codeVerifier: verifier
			});

			authWindow.close();
			return authResult;
		} catch (error) {
			authWindow.close();
			throw error;
		}
	}

	async listenForAuthCode(navigateUrl, authWindow) {
		// Set up custom file protocol to listen for redirect response
		const authCodeListener = new CustomProtocolListener();
		const codePromise = authCodeListener.start();
		authWindow.loadURL(navigateUrl);
		const code = await codePromise;
		authCodeListener.close();
		return code;
	}
	// Listen for authorization code response from Azure AD

	/**
	 * Handles the response from a popup or redirect. If response is null, will check if we have any accounts and attempt to sign in.
	 * @param response
	 */
	async handleResponse(response) {
		if (response !== null) {
			this.account = response.account;
		} else {
			this.account = await this.getAccount();
		}

		return this.account;
	}

	/**
	 * Calls getAllAccounts and determines the correct account to sign into, currently defaults to first account found in cache.
	 * https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-common/docs/Accounts.md
	 */
	async getAccount() {
		const cache = this.clientApplication.getTokenCache();
		const currentAccounts = await cache.getAllAccounts();

		if (currentAccounts === null) {
			console.log('No accounts detected');
			return null;
		}

		if (currentAccounts.length > 1) {
			// Add choose account code here
			console.log('Multiple accounts detected, need to add choose account code.');
			return currentAccounts[0];
		} else if (currentAccounts.length === 1) {
			return currentAccounts[0];
		} else {
			return null;
		}
	}
}

Reproduction Steps

try to login
prompt will open to select an account to select
I click the close button or back button
popup will close successfully
repeat step 1 again
prompt will open to select an account to select
select the account and sign in
the sign-in will stop and i can't login again until i restart my app

Expected Behavior
Login Again Successfully
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Other
Regression
No response
Source
External (Customer)

@mustafaAly I'm not sure I understand what the issue is. Msal-node does not provide popup handling code, can you please clarify what you believe is a bug in MSAL?

i handled popup handling by CreateAuthWindow Function
static createAuthWindow() {
return new BrowserWindow({
width: 400,
height: 600
});
}

@mustafaAly Can you please clarify what you believe is a bug in MSAL?

@tnorling I can reproduce this with our electron samples (@mustafaAly I assume your app is based on this sample -in that case the sample is outdated and there is currently a PR underway to fix that). It looks like the app hangs inside the protocol listener when trying to obtain the auth code. The reason seems to be that, when the user cancels the first sign-in attempt, the code does not catch the exception thrown and unregister the existing protocol before creating a new one, so it keeps listening without ever resolving.
So first of all please checkout either the Electron TypeScript sample here or the PR for Electron JavaScript sample. Then, inside the start() method of CustomProtocolListener, add the line for unregistering the protocol if auth code is not obtained:
class CustomProtocolListener {
  hostName;
  constructor(hostName) {
    this.hostName = hostName; //A string that represents the host name that should be listened on (i.e. 'msal' or '127.0.0.1')
  }

  // ...
  start() {
    const codePromise = new Promise((resolve, reject) => {
      protocol.registerStringProtocol(this.host, (req, callback) => {
        const requestUrl = new URL(req.url);
        const authCode = requestUrl.searchParams.get("code");

        if (authCode) {
            resolve(authCode)
        } else {
            protocol.unregisterProtocol(this.host);
            reject(new Error("No code found in URL"));
        }

      });
    });

    return codePromise;
  }

// ...

We will update both samples to handle this case properly.

Hi @derisen I tried this solution and it didn't resolve the issue
I found that when I make this scenario again and run this function
async getTokenInteractive(tokenRequest) {
	// Generate PKCE Challenge and Verifier before request
	const cryptoProvider = new CryptoProvider();
	const { challenge, verifier } = await cryptoProvider.generatePkceCodes();
	const authWindow = AuthProvider.createAuthWindow();

	// Add PKCE params to Auth Code URL request
	const authCodeUrlParams = {
		...this.authCodeUrlParams,
		scopes: tokenRequest.scopes,
		codeChallenge: challenge,
		prompt: "select_account",
		codeChallengeMethod: "S256"
	};

	try {
		// Get Auth Code URL
		const authCodeUrl = await this.clientApplication.getAuthCodeUrl(authCodeUrlParams);

		const authCode = await this.listenForAuthCode(authCodeUrl, authWindow);

		// Use Authorization Code and PKCE Code verifier to make token request
		const authResult = await this.clientApplication.acquireTokenByCode({
			...this.authCodeRequest,
			code: authCode,
			codeVerifier: verifier
		});

		authWindow.close();
		return authResult;
	} catch (error) {
		authWindow.close();
		throw error;
	}
}

------------------------ it gives me exception message
stack:'ServerError: invalid_grant: 501481 - [2022-06-01 11:13:52Z]: AADSTS501481: The Code_Verifier does not match the code_challenge supplied in the authorization request.\r\nTrace ID: 0c62d117-034a-487e-8df4-06197cc0b500\r\nCorrelation ID: 82aa83bd-2393-405b-b74e-100c4bd83186\r\nTimestamp: 2022-06-01 11:13:52Z - Correlation ID: 82aa83bd-2393-405b-b74e-100c4bd83186 - Trace ID: 0c62d117-034a-487e-8df4-06197cc0b500\n    at ServerError.AuthError [as constructor] (d:\Projects\Bitbucket\ut-hub\electron\node_modu…jects\Bitbucket\ut-hub\electron\node_modules\@azure\msal-common\dist\index.cjs.js:5093:41)\n    at step (d:\Projects\Bitbucket\ut-hub\electron\node_modules\@azure\msal-common\dist\index.cjs.js:79:23)\n    at Object.next (d:\Projects\Bitbucket\ut-hub\electron\node_modules\@azure\msal-common\dist\index.cjs.js:60:53)\n    at fulfilled (d:\Projects\Bitbucket\ut-hub\electron\node_modules\@azure\msal-common\dist\index.cjs.js:50:58)\n    at processTicksAndRejections (internal/pr...
any help?
thanks in advance

@mustafaAly this is a separate issue, but I'm not able to reproduce it with our electron sample -can you please try reproducing this with the ElectronTestApp sample and start another issue thread if you can?

yeah sure let me check

hey folks, I am facing the same issue here with the sample code.
Were you able to find a fix for this @mustafaAly ?

@imrans110 can you please create a new issue and provide details?

authors: derisen imrans110 mustafaAly tnorling


text:
FOCI feature and AppMetadata support in cache

This PR has changes to:

Create AppMetadata cache when Foci is sent in the sever response
Modified CacheManager to read cache data with helpers
Added unit tests

Coverage decreased (-0.5%) to 82.878% when pulling 71b97268aa726b72cecae75986f5cad923899d4f on appmetadata-foci into 1c1a65f9ccdf7f31b53e10f0a1fe5397afd4d788 on dev.

authors: coveralls sameerag


text:
Sound Regeler fehlerhaft

What is going on
"Audio Regler" doesn't safe the settings after changing it and switching menu´s
"Audio Changes" doesnt work as intended

Audio doesnt stop if I deactivate sound
Audio Menu doesnt work in the ESC menu at all

What should happen
Additional Information
I think Lucas already knows about the Problems, im just putting it here to be sure

funktioniert jz bei mir aufeinmal

Ist das nochmal aufgetreten? Sonst kannst du das issue auch closen @NamoPhoenix .


text:
Other LLM provider seems not  correct

Because OpenAI Api was banned in CN,  I use Qwen Api provided by Alibaba as my llm provider. But some errors occur in command line. Is the provider not good enough so that it cannot reason correctly?

Thanks for reaching out. It seems that the action is not generated correctly. The action should be ["open_feishu_assistant_app()"] instead of ["action(open_feishu_assistant_app())"]. Maybe you need to modify the prompt to emphasize this. It seems that Qwen cannot strictly follow the instructions and output the answer in the correct format, which is a common issue for small models.

Because OpenAI Api was banned in CN, I use Qwen Api provided by Alibaba as my llm provider. But some errors occur in command line. Is the provider not good enough so that it cannot reason correctly?

I am also trying to use qwen api.I simply change the api_key and base_url ,but it seems doesn't work.Would you like to tell me what you did to adapt to qwen api?

Because OpenAI Api was banned in CN, I use Qwen Api provided by Alibaba as my llm provider. But some errors occur in command line. Is the provider not good enough so that it cannot reason correctly?

I am also trying to use qwen api.I simply change the api_key and base_url ,but it seems doesn't work.Would you like to tell me what you did to adapt to qwen api?

I am testing Stardew Valley using the 'qwen-vl-max' model, but after the character comes out of the house, there are no further actions, and the task of clearing the farm has not been completed. It seems that the model's intelligence might be insufficient? (By the way, during the test, 196 queries consumed 170,000 tokens, so the cost could also be a significant issue.)
目前我遇到的问题仅供参考：
1.修改api_key和base_url
self.client = OpenAI(
api_key= "sk-",  # 如果您没有配置环境变量，请在此处用您的API Key进行替换
base_url="https://dashscope.aliyuncs.com/compatible-mode/v1",  # 填写DashScope服务的base_url
)
2. 修改embedding接口的参数为字符串列表
texts_batch = [encoding.decode(t) for t in tokens[i: i + self.chunk_size]]
response = self.embed_with_retry(
input=texts_batch,
**self._emb_invocation_params,
)
千问的embedding接口目前仅支持两种输入，分别是字符串、字符串列表，要转成字符串列表
3.修改openai_config.json
"emb_model": "text-embedding-v3",
"comp_model": "qwen-vl-max",
用到了图片识别需要用qwen-vl-max模型
4.删除res/stardew/skills/skill_lib.json
千问的embedding接口默认返回1024长度会和之前的缓存冲突
5.文件.env设置好窗口名称
IDE_NAME = "Cradle"
我用PyCharm打开Cradle项目（不点开任何文件）窗口名称是“Cradle”所以我设置为“Cradle”
如果设置不正确会报以下错误（我不知道找这个窗口是干嘛的修改只是为了不报错）
ide_window = io_env.get_windows_by_name(ide_name)[0]
IndexError: list index out of range

Because OpenAI Api was banned in CN, I use Qwen Api provided by Alibaba as my llm provider. But some errors occur in command line. Is the provider not good enough so that it cannot reason correctly?

I am also trying to use qwen api.I simply change the api_key and base_url ,but it seems doesn't work.Would you like to tell me what you did to adapt to qwen api?

Because Qwen api is similar to Openai api, I just copy the cradle/provider/llm/openai.py as qwen.py and modify some codes. And then add qwen.py to llm_factory.py . Note that you need to read qwen docs.

Because OpenAI Api was banned in CN, I use Qwen Api provided by Alibaba as my llm provider. But some errors occur in command line. Is the provider not good enough so that it cannot reason correctly?

I am also trying to use qwen api.I simply change the api_key and base_url ,but it seems doesn't work.Would you like to tell me what you did to adapt to qwen api?

If I have any time, I will share my code on github. Then you can check my code to modify your own.

authors: BruceWayneZero KJinze Skylarking WeihaoTan

repo: BAAI-Agents/Cradle


text:
SciPy-1.6 version breaks WXRotation

The new SciPy release is not compatible with our WXRotations object. Some interfaces changed and some functions seem to be removed or renamed.

I think this has already been addressed upstream, but is not yet released https://github.com/scipy/scipy/commit/1d4e9df17b3f8ae2e6b27621c2cde9cf1df6c9a6
cref: https://github.com/asdf-format/asdf/issues/916

Upstream issue (scipy) is fixed, now we have to way for a release :)

@marscher They released version 2.7.3 recently that includes the fix

https://github.com/asdf-format/asdf/issues/916#issuecomment-786161684 and re-opened the issue

we will do a patch release to unpin scipy in the requirements after their next release 🚀

it appears scipy has assigned the fix to their 1.7.0 milestone which could some time to release
Should we ask to include this into 1.6.2 @marscher ? IIRC there are no breaking changes introduced with this fix right?

On 3/15/21 1:47 PM, Cagtay Fabry wrote:

it appears scipy has assigned the fix to their 1.7.0 milestone which could take some time to release
Should we ask to include this into 1.6.2 @marscher ? IIRC there are no breaking changes introduced with this fix right?

No it does not brake any previous assumptions, so I can try asking for
it. Thanks for looking into it.

authors: CagtayFabry marscher vhirtham

repo: BAMWelDX/weldx


text:
feature/BA-977

Bootstrap 4 Styling - Update Users Module (Authentication)
Fixes BA-977

Looks good.  Merged to develop.

This has been merged but some reason the PR doesn't detect that... closing for now.  Changes are in develop.

authors: mark-a-wilson sutherlanda

repo: BCDevExchange/devex

license_source: bigquery


text:
fix: episode with version and between in two space

兼用了下这种带版本号又位于俩空格之间的剧集数格式，测试也加上了，看着应该没影响到其他格式的处理。
 [喵萌Production&LoliHouse] 偶像大师 灰姑娘女孩 U149 / THE IDOLM@STER CINDERELLA GIRLS U149 - 04v2 [WebRip 1080p HEVC-10bit AAC][简繁日内封字幕]

已经关电脑了，你更新一下版本号推个tag发个新版吧

有release ci，只需要更新pyproject，推个新tag就行。

好嘞~

repo: BGmi/anime-episode-parser


text:
Sphinx documentation build

Here is a Sphinx-based documentation build. You can build the documentation locally by creating a virtualenv, installing the dependencies in docs/requirements.txt, and then running make html in the doc subdirectory. The included .readthedocs.yml file should be a good first stab at a working RTD configuration, but you'll have to set that up on RTD and test.
I got some errors on some of the imports, where it's unclear whether you're importing a module or a class, so I fixed those, and there's no .gitignore so I added one with at least one directory type that should be ignored.

Actually, it seems like flake8 disagrees.

Actually, it seems like flake8 disagrees. And the second commit seems a bit confused.

I'm not sure what this refers to, the second commit? Something weird definitely happened to the commit message :smile:. Probably hit the wrong key in vim.
The issue here is that you have a module named transiflow.Discretization with inside of it a class Discretization. You then import that class in transiflow/__init__.py and re-export it as transiflow.Discretization. So is transiflow.Discretization now a class or a module?
At any rate, module names should be lowercase in Python, I'm surprised flake8 isn't complaining about that but I haven't checked the configuration.

Ah, I see, Sphinx generates a configuration file that isn't PEP-8 compliant. Not ideal. I've pushed a fix.

Actually, it seems like flake8 disagrees. And the second commit seems a bit confused.

I'm not sure what this refers to, the second commit? Something weird definitely happened to the commit message 😄. Probably hit the wrong key in vim.

The flake8 warnings from the CI are about the first commit.

The issue here is that you have a module named transiflow.Discretization with inside of it a class Discretization. You then import that class in transiflow/__init__.py and re-export it as transiflow.Discretization. So is transiflow.Discretization now a class or a module?
At any rate, module names should be lowercase in Python, I'm surprised flake8 isn't complaining about that but I haven't checked the configuration.

Discretization.py is just a file that stores the Discretization class. It shouldn't be treated as a module. I assume the "Pythonic" way would be to dump everything into a single file and then you'd have classes that are not modules. I don't like this idea. If there is a better way to do this, I'd like to hear about it.

A Python file is a module (namespace that you can import things from), and a directory is a package (not to be confused with the thing you download from PyPI) if it has a __init__.py file in it. You cannot change that, and you don't want to, because it would confuse the heck out of anyone else with some Python experience trying to read your code. When in Rome...
A class is not a module, but it always is inside of a module, and you can import it from there in another module if you need it. So Python modules tend to be much more fine-grained and hierarchical than e.g. C++ namespaces, where you often have many files declaring things in the same namespace. But C++ is a bit of an odd duck in that respect, Java maps packages to directories too for example. (And Java enforces one-class-per-file, which I personally think is a bit much, and I'm happy that Python will let me put a few auxiliary classes together with the main one in a file.)
If you want to have a complex implementation spread out across many files, but want to have a single user-facing namespace API (as you usually do), then you import the public symbols from the various modules in which they're defined into your top-level package's __init__.py, so that they can be imported from there too, and then you tell your users to do just that. We have such a set-up here already (although perhaps transiflow.interface is also supposed to be public?).

So I either put everything in the __init__.py file, or I leave it as is (possibly with lower case file names, but titlecase class names). As I don't want to expose the "modules" to the users, I don't think it's an issue either way.

You could put everything in the __init__.py directly, but it would end up a very large file, and I'd consider it bad style.
If you want to signal to the user that they should not import something from a particular file/module, then the standard way to do that is to give it a name starting with a single underscore (this works for entire modules, packages, or individual symbols).
That doesn't actually make it private, and Python won't complain if they import it anyway, but if you change the code and release a new version that changes something in such a file then you can rightfully say that it's their own fault their code is now broken, as they knew it wasn't part of the API :smile:.

authors: LourensVeen Sbte

repo: BIMAU/transiflow


text:
请教一下

我是一个计算机的初学者
我十分喜欢您的博客风格
但是我不太会JS配置
您能仔细说说吗
谢谢
ps：QQ2953846540

如果有疑问，可以博客园私我，我会回复的！

authors: BNDong NOIP-shl

repo: BNDong/Cnblogs-Theme-SimpleMemory


text:
Refactoring maps code

The MapsController has some code which can be optimized to work more effectively. The complex if statement can be simplified and the gmaps code moved to a helper

This has been pushed live in production and is working successively

repo: BOWiki/BOW


text:
Add initial support for deployment of ESB Toolkit 2.0 itineraries

Add support for deployment of ESB Toolkit 2.0 itineraries.  Add a new ItemGroup , new  property, read ESB Toolkit registry key for install path, call EsbImportUtil.exe for deploy and undeploy.
This work item was migrated from CodePlex
CodePlex work item ID: '6167'
Assigned to: 'tfabraham'
Vote count: '0'

[UnknownUser@3/10/2010]
Resolved with changeset 38078.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]

repo: BTDF/DeploymentFramework


text:
data Z-score normalization

hi @aptx1231 :
In wpf_dataset.py, why are the mean and variance of node features calculated for all features of the node rather than for each feature of the node
self.data_mean = np.expand_dims( # (1, 134, 1, 1)
np.mean(
data[:, border1s[0]:border2s[0], 2:],
axis=(1, 2),
keepdims=True),

self.data_scale = np.expand_dims( # (1, 134, 1, 1)
np.std(data[:, border1s[0]:border2s[0], 2:],
axis=(1, 2),
keepdims=True),

Both methods were tried, but it was found that all the features together for the mean-variance worked better.

@aptx1231 thank you for your help


text:
solution for even_fibonacci_nums

fixed bug in even_fibonacci_nums

Hey, please mention the issue number solved.

#94

the output is wrong. so I'm closing the PR.


text:
OSError: exception: access violation reading 0xFFFFFFFFFFFFFFFF

C:\Users\木羊羽\AppData\Local\Programs\Python\Python39\python.exe D:/Multifarious/Python/测试.py
Traceback (most recent call last):
File "D:\Multifarious\Python\测试.py", line 3, in
converter.convert('汉字')  # 漢字
File "C:\Users\木羊羽\AppData\Local\Programs\Python\Python39\lib\site-packages\opencc_init_.py", line 87, in convert
retv_i = libopencc.opencc_convert_utf8(self.od, text, len(text))
OSError: exception: access violation reading 0xFFFFFFFFFFFFFFFF
Exception ignored in: <function OpenCC.del at 0x0000029D97A14430>
Traceback (most recent call last):
File "C:\Users\木羊羽\AppData\Local\Programs\Python\Python39\lib\site-packages\opencc_init.py", line 99, in del
OSError: exception: access violation reading 0xFFFFFFFFFFFFFFFF

我这里用最新版的main分支的代码编译出来的lib也是这个错误，用C++、C调用都是这个错误。

我的沥青款类似，如果opencc库安装到中文路径，调用的时候
libopencc.opencc_close(self._od)
OSError: exception: access violation reading 0xFFFFFFFFFFFFFFFF

我这里用最新版的main分支的代码编译出来的lib也是这个错误，用C++、C调用都是这个错误。
原因是不能只有一个s2t.json文件，这个文件目录下的其他文件比如STPhrases.ocd2也是需要的。

原因是opencc库安装到中文路径

repo: BYVoid/OpenCC


text:
Node._cache is nulled by TransformNode

Hi,
A TransformNode instance will null its _cache property when disposed (see TransformNode.dispose)
As a consequence, calling some method (like computeWorldMatrix) on a disposed TransformNode will cause a Javascript error
While it can be considered to be by design, please note it was possible to call computeWorldMatrix on a disposed mesh in last stable version (see playground below).
http://playground.babylonjs.com/indexstable#SY6SYY

It is by design and for memory reason. Disposing an object means you don't want it anymore and thus there is no guarantee about the availability f the object.

authors: SvenFrankson deltakosh


text:
Making data Nullable for RawTexture3D and RawTexture2DArray

This change will make creating RawTexture3D and RawTexture2DArray storage textures less tedious when setting the data in a compute shader. This also brings it more in line with the RawTexture constructor.
https://doc.babylonjs.com/typedoc/classes/BABYLON.RawTexture#constructor
Related to this change that allows RawTexture3D and RawTexture2DArray to be flagged as storage textures.
https://github.com/BabylonJS/Babylon.js/pull/14070

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14072/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14072/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14072/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14072/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14072/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14072/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14072/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14072/merge#BCU1XR#0

I am not too sure we should add the 2 static functions here as they are only shortcuts for functions which are not currently used a lot.
@RaananW what do you think ?

Not sure how much these functions are needed, especially since they are just a proxy to the constructor, passing the variables you are passing anyhow. Why won't the dev use the constructor directly?

I added the static functions because I am currently using their analog in RawTexture. They aren't necessary, though. I can remove them.

authors: RaananW bjsplat christianphalv


text:
First version of module-testing

There are curently two tests that are running one after the other -

vanilla-typescript that loads the dependencies and calling the runTests function wit the global namespace
webpack-typescript that bundles the dependencies and loading them using es6 imports.

the source is being compiled and bundled (when using a bundler).
There are two iunternal tests running - checking that the dependencies actually loaded, and loading a GLTF model.
Further tests will be added shortly.
At the moment this is not part of the "tests" task. to trigger this test, call gulp tests-modules.

OK to merge?

This and the gulp 4 branch will conflict. Both are ok to merge, I just need to know which one is being merged first :smile:

merge in the order you want:)

I will merge this branch to the gulp 4, fix conflicts and merge to master

Closing this PR

authors: RaananW deltakosh


text:
Master

Initial toolkit documentation - under construction

Hey Delta... I am trying to upload the starter docs for the toolkit. I guess i dont have rights to modify the statics.json and the original unity.md
Can you please take care of that :)

There is no right on files. You should be able to modify all of them (just do not forget to do a git pull first)

Ping @babylonjsguide for review

I will do the PR

repo: BabylonJS/Documentation


text:
Hotfix: remove tree balance rewards

Temporarily disable tree rewards until a caching solution is developed

LGTM

repo: Badger-Finance/badger-rewards


text:
Fix offset_encoding being non-optional in nightly neovim

Small fix for https://github.com/neovim/neovim/issues/14090#issuecomment-1012005684, otherwise this plugins is failing on nightly neovim

If I merge this it will fail on other releases. I believe the proper fix should be to replace the text edit function with our own implementation (#12)

Yes, i just took out the neovim's old implementation for now so that it will work on old and nightly releases. Appreciate it if you can try it out.
Thanks for the PR and bringing it out for the attention btw

authors: Badhi JafarAbdi

repo: Badhi/nvim-treesitter-cpp-tools


text:
pod 'BaiduMapKit'最新版4.1.0和pod 'BMKLocationKit'冲突

头文件导入冲突, duplicate symbol错误

最新版不是4.1.0吧

authors: OriTheElf harveyseeking

repo: BaiduLBS/BaiduMapKit

license: mit


text:
INPUT-OUTPUT gets parsed as an error

For example, in the code:
class MyEntityClass:
    method public void Fetch(input-output dataset dsMyDataset,
                             poParameter as myParameter):

    end method.
end class.

It would be advantageous if INPUT-OUTPUT would be added as a function_parameter_mode node.

Registered: https://github.com/usagi-coffee/tree-sitter-abl/issues/99

Fixed with version 0.0.45 of tree-sitter-abl

authors: eglekaz gustason

repo: BalticAmadeus/AblFormatter


text:
컴포넌트 비즈니스 로직 분리

✨ 개요
현재 페이지 파일만 비즈니스 로직을 분리하고 있습니다 하지만 한 파일에 너무 많은 양의 코드가 있어 읽기 어려우며 비즈니스 로직도 파악이 어려워져 컴포넌트 파일도 비즈니스 로직을 분리해야합니다
✅ 해야 할 일

[ ] 컴포넌트 비즈니스 로직 분리

🙋🏻 덧붙일 말
No response

@SEOKKAMONI 거의 다되어가네용ㅎㅎ
좀만 더 힘내세요오!!

repo: Bamdoliro/marururu


text:
SettlementComponent Audit

For New Contributors
How to contribute
Description

Create an auditor that compares all values for all settlementcomponents on the server and client.
Copy https://github.com/Bannerlord-Coop-Team/BannerlordCoop/tree/development/source/GameInterface/Services/Armies/Audit to the settlements folder and use that as a template
Intended Design

N/A
Location

Create a branch based from development
Related Issues

N/A
Requirements

N/A
Additional information

N/A
Definition of Done

[ ] Class level comments exist for all new classes.
[ ] XUnit tests exist for every method that does not require the game to be ran.

Assign me, please

authors: MaxDorob samuelzurowski

repo: Bannerlord-Coop-Team/BannerlordCoop


text:
🛑 Hay River Health and Social Services Authority is down

In a9d5329, Hay River Health and Social Services Authority (https://www.hrhssa.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Hay River Health and Social Services Authority is back up in 36265e8 after 9 minutes.

repo: Barctic/gnwt-monitor


text:
🛑 NWT Housing Corporation is down

In cad665e, NWT Housing Corporation (https://www.nwthc.gov.nt.ca) was down:

HTTP code: 503
Response time: 9846 ms

Resolved: NWT Housing Corporation is back up in a3284c7 after 28 minutes.


text:
🛑 Health and Social Services is down

In f05dbf6, Health and Social Services (https://www.hss.gov.nt.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Health and Social Services is back up in 27e8f19 after 29 minutes.


text:
🛑 Industry, Tourism and Investment is down

In 47de1f1, Industry, Tourism and Investment (https://www.iti.gov.nt.ca) was down:

HTTP code: 504
Response time: 295 ms

Resolved: Industry, Tourism and Investment is back up in 43adfe1 after 19 minutes.


text:
🛑 Lands is down

In bbb4627, Lands (https://www.lands.gov.nt.ca) was down:

HTTP code: 503
Response time: 8661 ms

Resolved: Lands is back up in e99f510 after 40 minutes.


text:
🛑 NWT Housing Corporation is down

In cdf1d1c, NWT Housing Corporation (https://www.nwthc.gov.nt.ca) was down:

HTTP code: 403
Response time: 280 ms

Resolved: NWT Housing Corporation is back up in e4b839e.


text:
🛑 GNWT Main Page is down

In 40bd26d, GNWT Main Page (https://www.gov.nt.ca) was down:

HTTP code: 403
Response time: 429 ms

Resolved: GNWT Main Page is back up in c2819ba.


text:
🛑 Industry, Tourism and Investment is down

In 4a249bc, Industry, Tourism and Investment (https://www.iti.gov.nt.ca) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Industry, Tourism and Investment is back up in 051aaab.