primordic/IssueDupesLite huggingface dataset:
Repository: AxonFramework/AxonFramework

Issue #1850: @ExceptionHandler methods don't invoke on exception during aggregate creation 
Created: 2021-06-21T14:45:46Z
Basic information

Axon Framework version: 4.5.2
JDK version:  11
Complete executable reproducer if available (e.g. GitHub Repo): NA

If an exception is thrown during aggregate creation, exception handling methods are not invoked. It does not matter if the aggregate creation is done via constructor or class method. It also does not matter if the exception handling method is in the aggregate class itself or somewhere else.  In all cases and combinations, at no time is the exception handling method invoked.
The issue isn't environmental as I could get exception handler methods to invoke when exceptions are thrown by any command handler AFTER the initial aggregate creation command has completed successfully.
Steps to reproduce

Setup an Aggregate to throw an exception during creation (e.g. IllegalArgumentException or similar). Create an @ExceptionHandler method on the aggregate that expects this exception. Also, put a similar exception handling method in another class (e.g. a Spring `@Component)
Send a message to this aggregate that results in this exception being thrown

BTW, I also tried using a MessageDispatchHandler for input checking and throwing an exception there instead of inside the aggregate @CommandHandler method. This did not work either.
Finally, I also tried Springs own @ExceptionHandler mechanism and that also didn't work.

Expected behaviour

One or both of the @ExceptionHandler methods should invoke
Actual behaviour

No exception handler methods get invoked at all
Example Aggregate
@Aggregate
public class GiftCard {

    public GiftCard() { }

    @AggregateIdentifier
    private String id;

    @CommandHandler
    public GiftCard(IssueCardCommand command) {
        if (command.getAmount() <= 0) {
            throw new IllegalArgumentException("amount <= 0");
        }
        apply(new CardIssuedEvent(command.getCardId(), command.getAmount()));
    }

    @ExceptionHandler(value = IllegalArgumentException.class)
    public void on(IllegalArgumentException ex) {
        // WE NEVER GET HERE
        throw new IllegalStateException("CREATED IN EXCEPTION HANDLER");
    }

    @EventSourcingHandler
    public void on(CardIssuedEvent event) {
        id = event.getCardId();
    }

}
Example Test
    @Test
    void shouldHandleErrorGiftCard() {
        fixture.givenNoPriorActivity()
                .when(new IssueCardCommand("cardId", -100))
                .expectException(IllegalStateException.class);
    }

Duplicate issue #1865: AggregateTestFixture: CommandHandlerInterceptor doesn't intercept commands defined on constructor
Created: 2021-07-07T07:39:03Z
Basic information

Axon Framework version: 4.5.1

Steps to reproduce
create a @commandHandlerInterceptor that wants to intercept a command on the constructor of the aggregate.
Expected behaviour
The command is intercepted in a test with AggregateTestFixture.
Actual behaviour
The command is not intercepted.

Closing comment (2021-07-07T13:32:02Z): Duplicate of #1850.
Repository: AxonFramework/AxonFramework

Issue #511: Add toString() for implementations of org.axonframework.messaging.Message
Created: 2018-02-20T15:12:12Z
For debugging/logging purposes it would be useful to have a reasonable toString implementation for messages which is currently missing.
Looking at the source code org.axonframework.messaging.MessageDecorator could be a good start -
maybe the class of the message itself and the payload type should be included.
Are there further thoughts on the matter?

Duplicate issue #514: Axon-Test: Fixture returns "DomainEventMessage" as type if expectEventsMatching() fails
Created: 2018-02-22T09:49:34Z
When using expectEventsMatching() on an AggregateTestFixture the result of an failure matching the given events always is GenericDomainEventMessage
List with Messages with Payloads matching <list with exact sequence of: <[matches a given predicate]>, <[matches a given predicate]> (FAILED!) and <<nothing>>>
But got:
GenericDomainEventMessage: org.axonframework.eventsourcing.GenericDomainEventMessage@20f5281c
GenericDomainEventMessage: org.axonframework.eventsourcing.GenericDomainEventMessage@56c4278e

This makes it hard to get what is going on and to find out what kind of event was published.
Cause:
ResultValidatorImpl uses Reporter.reportWrongEvent() to format the output message. The reporter prints publishedEvent.getClass().getSimpleName() and publishedEvent.toString() which has to be a EventMessage class.
Solution:
It should print payloadType() and payload().toString().
ResultValidatorImpl knows the type is EventMessage but  Reporter.reportWrongEvent() uses Collection<?> for the actualEvents input parameter. This easily can be typed to List<EventMessage<?>>.

Closing comment (2018-02-22T18:56:57Z): I think this is a duplicate of #511. Can you confirm that is what you meant?
Repository: AxonFramework/AxonFramework

Issue #314: Allow command handlers to be declared at different levels of aggregate class hierarchy
Created: 2017-03-23T22:36:16Z
Per the discussion in https://groups.google.com/d/topic/axonframework/FhWk-OMPgZc/discussion -- in Axon 2 it was possible to have an aggregate class hierarchy where common command handlers were declared on the superclass and subclass-specific command handlers were declared only on the relevant subclass, and Axon would figure out which aggregates could handle which commands.
Axon 3 requires all the command handlers to be declared on the superclass, which aside from breaking encapsulation means that any command that is relevant to any subclass can potentially be delivered to aggregate instances of any other subclass.

Duplicate issue #943: Axon + Spring and Inheritance - switches aggregate type in the event store
Created: 2018-12-31T09:57:31Z
All,
We encountered the following issue during command handling in Axon.
Let's say we have the following class hierachy:
public abstract class Animal {

    @CommandHandler
    public void handle(Move command) {
        AggregateLifecycle.apply(new AnimalMoved(command.animalId));
    }

}


public class Dog extends Animal {

    @AggregateIdentifier
    private AnimalId dogId;

    private Dog() {
    }

    @CommandHandler
    public Dog(CreateDog command) {
        AggregateLifecycle.apply(new DogCreated(command.animalId));
    }

    @EventSourcingHandler
    private void on(DogCreated event) {
        this.dogId = event.animalId;
    }
}


public class Horse extends Animal {

    @AggregateIdentifier
    private AnimalId horseId;

    private Horse() {
    }

    @CommandHandler
    public Horse(CreateHorse command) {
        AggregateLifecycle.apply(new HorseCreated(command.animalId));
    }

    @EventSourcingHandler
    private void on(HorseCreated event) {
        this.horseId = event.animalId;
    }
}

For this structure Axon finds that both the classes Horse and Dog can handle the move command. On this it applies the "last one wins".
As a consequence when we apply the Move command on a Dog Aggregate instance it gets saved into the event store as an AnimalMoved event with aggregateType "Horse" (in other words it switches the aggregate type).
Our applications are setup on Axon 4.0.3 and Spring boot 1.5.9
Robin

Closing comment (2018-12-31T14:29:22Z): I believe this is a duplicate of #314. As such, I've marked it as a duplicate and will close the issue.
Nonetheless, that you've marked to me suggests we might move #314 a bit higher up in the to-do list.
Thus thanks for filing this issue @rcusters!
Repository: AxonFramework/AxonFramework

Issue #952: axon-server-connector GrpcExceptionParser causes Null pointer exception when serialising exception from server
Created: 2019-01-09T03:03:46Z
I'm getting a NullPointerException which is wrapping (and so hiding) exceptions that I get from the Axon Server (version 4.0).
The issue is that org.axonframework.axonserver.connector.event.util.GrpcExceptionParser#parse calls org.axonframework.axonserver.connector.ErrorCode#convert(java.lang.Throwable)
to convert to an Axon Exception.  This convert method passes null as the 'source' which results in a NPE here io.axoniq.axonserver.grpc.ErrorMessage.Builder#setLocation
Suggest org.axonframework.axonserver.connector.event.util.GrpcExceptionParser#parse should call the overload method 'convert' and pass a non null source.

FYI (if it helps to reproduce) the original exception from Axon Server logged out :
2019-01-09 13:41:34.005  WARN 14492 --- [worker-ELG-3-10] i.a.a.localstorage.LocalEventStore       : Error while storing events: [AXONIQ-2000] Invalid sequence number 0 for aggregate 05c820c7-ffa7-449e-84ab-8fc7be013d29, expected 2 2019-01-09 13:41:34.006  WARN 14492 --- [worker-ELG-3-10] i.a.a.message.event.EventDispatcher      : Error on connection from event store: [AXONIQ-2000] Invalid sequence number 0 for aggregate 05c820c7-ffa7-449e-84ab-8fc7be013d29, expected 2
Cheers

Duplicate issue #956: AXONIQ-2000 on querying with axon-server auto-conf
Created: 2019-01-13T12:33:35Z
Using axonframework 4.0.3 with axon-server-connector results in AXONIQ-2000 (by the meaning: event sequence is 0 and not 1) when dispatching on queryGateway. In fact looking into axon-server backend shows that all events have sequence number zero.
Showcase:
https://github.com/janesser/axon-ping-example/blob/995b6c230fcf67847b51fc804985387588a52490/src/main/java/de/esserjan/edu/axon/distributed/rest/PingController.java#L48
Not sure what i am missing, either a piece of config or some detail in the command-event-structure.
Eventually it is a bug.
Support would be very welcome.

Closing comment (2019-01-14T12:00:14Z): Seems related to #952
(same stack-trace)
Still puzzled as i am using the version 4.0.3.
Appearently i can only send the PingCommand to PingAggregate once. Every succeeding call would fail. What exactly is the restriction here?
Repository: AxonFramework/AxonFramework

Issue #2430: Upgrade to Spring 6 and Spring Boot 3
Created: 2022-10-07T11:26:44Z
We should investigate the effort to upgrade to Spring 6 and Spring Boot 3.
Both versions make some rough internal adjustments when it comes to JDK version subsequently the Javax/Jakarta switch.
As Axon Framework hasn't made that transition yet, there's a chance we need to introduce an additional module, dedicated to these new versions.

Duplicate issue #2524: Spring Boot 3 update causes the build to fail
Created: 2022-12-16T08:32:37Z
Basic information

Axon Framework version: Latest 4.6.2
JDK version:  17
Complete executable reproducer if available (e.g. GitHub Repo): jesperancinha/video-series-app#34

Steps to reproduce
Just run the maven build
mvn clean install
Expected behaviour
It should scan components and configuration automatically
Actual behaviour
The first error it throws is:
Parameter 0 of constructor in org.jesperancinha.video.command.rest.VideoSeriesController required a bean of type 'org.axonframework.commandhandling.gateway.CommandGateway' that could not be found.
However, there are a lot of beans that it just does not initializes. Up until spring-boot 2.7.6,  there were no issues but since 3.0.0, there appear to be problems with the scanning.

Closing comment (2022-12-16T08:40:28Z): I will be closing this issue as a duplicate of #2430.
As you can see from the referred issue, @jesperancinha, we aim to provide Spring Boot 3 and Spring Framework 6 support in 4.7.0.
As such, you're, for the time, unable to combine both.
Release-wise, we aim for a date somewhere in/near January next year.
Repository: Azure-Samples/cognitive-services-speech-sdk

Issue #2265: "Hey Siri" stops working when using keyword recognition
Created: 2024-02-10T16:52:06Z
Describe the bug

Set up Siri and make sure she responds to "Hey, Siri".
Launch VS Code with VS Code Speech installed.
Set accessibility.voice.keywordActivation to "chatInContext". (Probably anything other than "off" will do the trick.)
Say "Hey, Siri". Siri will not respond.

To Reproduce
Steps to reproduce the behavior:

open VS Code
install GitHub Copilot Chat and VS Code Speech extension
accessibility.voice.keywordActivation to "chatInContext"

Expected behavior
"Hey Siri" should still work.
Version of the Cognitive Services Speech SDK
1.33.x
Platform, Operating System, and Programming Language
Darwin arm64 23.3.0
Additional context
Originally reported as microsoft/vscode#204811
VS Code extension is using the Azure Speech SDK in C++ and the keyword recognition code is here: https://github.com/microsoft/node-speech/blob/22064207050a16d0b30b1305857bafbba07402c9/src/main.cc#L424

Duplicate issue #2266: Low quality when talking in MS Teams while keyword recognition
Created: 2024-02-10T16:55:31Z
Describe the bug

open VSCode, ensure that there's the micro icon appears on the system tray, and copilot voice chat in vscode is ok
join a Microsoft Teams meeting, the collegues says that they cannot hear you very clearly, even if you're not using vscode voice chat at that moment.
close VSCode, then collegues on Teams says it's good now.

To Reproduce
Steps to reproduce the behavior:

open VS Code
install GitHub Copilot Chat and VS Code Speech extension
accessibility.voice.keywordActivation to "chatInContext"

Expected behavior
Quality of voice recording in Teams should not degrade.
Version of the Cognitive Services Speech SDK
1.33.x
Platform, Operating System, and Programming Language
Windows 11
Additional context
Originally reported as microsoft/vscode#204722
VS Code extension is using the Azure Speech SDK in C++ and the keyword recognition code is here: https://github.com/microsoft/node-speech/blob/22064207050a16d0b30b1305857bafbba07402c9/src/main.cc#L424

Closing comment (2024-02-15T22:27:07Z): hi @bpasero, similar to #2265, this is related to how the OS handles audio and the mitigation would be to either stop recognizing/recording when losing focus.
Repository: Azure-Samples/cognitive-services-speech-sdk

Issue #468: Entity recognition broken when no intent recognized
Created: 2019-12-20T16:20:09Z
@jhakulin @rhurey From Thursday on the entity recgonition stopped working for LUIS EUW Xamarin SDK.
KeyRecognizedEvent?.Invoke(key, e?.Result.Properties.GetProperty(PropertyId.LanguageUnderstandingServiceResponse_JsonResult));
When trying to get the intents from a result the function returns null instead of the json result, when manually inspecting the element it looks fine ... -.-

And when an intent is recognized it returns  the function works like always and returns the proper json....
{
  "query": "erstelle eine neue aufgabe 2",
  "topScoringIntent": {
    "intent": "Todo_AddTodo",
    "score": 0.685601056
  },
  "entities": [
    {
      "entity": "aufgabe",
      "type": "builtin.keyPhrase",
      "startIndex": 19,
      "endIndex": 25
    },
    {
      "entity": "eine",
      "type": "builtin.number",
      "startIndex": 9,
      "endIndex": 12,
      "resolution": {
        "value": "1"
      }
    },
    {
      "entity": "2",
      "type": "builtin.number",
      "startIndex": 27,
      "endIndex": 27,
      "resolution": {
        "value": "2"
      }
    }
  ]
}


This is not the behavior expected nor what was happening until now....
P.s. we wanted to launch the first version of our application early next year... And now this is the second breaking error within a week... i'm getting a little nervous-.-

Duplicate issue #389: LUIS westeurope not working as westus
Created: 2019-10-01T14:14:59Z
Describe the bug
Hello,
so I've been using a LUIS app hosted in westus for the few days, but I wanted to switch to the european version. Signed up at eu.luis.ai and created an app. While the us app worked fine, the european app somehow didn't work with the same code.
I swapped out region, intent_id and app_id but the app doesn't recognize any speech or end of speech, it just starts a session and after that nothing, not output nor error messages.
To Reproduce
The code I used was from the python samples at https://github.com/Azure-Samples/cognitive-services-speech-sdk/blob/master/samples/python/console/intent_sample.py with recognize_intent_continuous() modified to work with my microphone
Expected behavior
A clear and concise description of what you expected to happen.
Version of the Cognitive Services Speech SDK
Speech SDK Release 1.7.0 for python
Platform, Operating System, and Programming Language

Windows 10

Closing comment (2020-01-22T00:45:11Z): Duplicate of #468
Repository: Azure-Samples/cognitive-services-speech-sdk

Issue #2170: [.NET 8] Warning: "Found version-specific or distribution-specific runtime identifiers"
Created: 2023-12-05T02:09:40Z
Describe the bug
Including the Microsoft.CognitiveServices.Speech NuGet package yields a build warning.
C:\Program Files\dotnet\sdk\8.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(284,5):
  warning NETSDK1206: Found version-specific or distribution-specific runtime identifier(s):
  centos7-x64, win10-arm, win10-arm64. Affected libraries: Microsoft.CognitiveServices.Speech.
  In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers
  will not be found by default. See https://aka.ms/dotnet/rid-usage for details.

To Reproduce

Create an empty .NET 8 Console App.
Install the Microsoft.CognitiveServices.Speech NuGet package.
Build the solution.

Expected behavior
No warnings!
Version of the Cognitive Services Speech SDK
Microsoft.CognitiveServices.Speech v1.33.0.
Platform, Operating System, and Programming Language

OS: Windows
Hardware: x64
Programming language: C#
Visual Studio 2022, .NET 8

I hope I'm posting this to the right place.  Thanks for your time!

Duplicate issue #2178: .NET SDK emits NETSDK1206 warning in .NET 8.0
Created: 2023-12-15T10:53:16Z
Greetings,
when using the current version of the .NET SDK, compiling a solution causes NETSDK1206 because the package references platform-specific components:
warning NETSDK1206: Found version-specific or distribution-specific runtime identifier(s): centos7-x64, win10-arm, win10-arm64. Affected libraries: Microsoft.CognitiveServices.Speech. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.
Is it feasible to remove these specific artifacts in the next version, to get rid of the warning?
Thanks in advance and all the best

Closing comment (2023-12-15T18:50:24Z): Duplicate of #2170
Repository: Azure-Samples/cognitive-services-speech-sdk

Issue #1925: 需要哪些lib呢  提示一堆无法解析的外部符号
Created: 2023-04-19T03:51:58Z
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

...
...

Expected behavior
A clear and concise description of what you expected to happen.
Version of the Cognitive Services Speech SDK
Which version of the SDK are you using.
Platform, Operating System, and Programming Language

OS: [e.g. Windows, Linux, Android, iOS, ...] - please be specific
Hardware - x64, x86, ARM, ...
Programming language: C#, C++, Java, JavaScript, Objective-C, Python
Browser [e.g. Chrome, Safari] (if applicable) - please be specific

Additional context

Error messages, stack trace, sample code to reproduce the issue, ...
Please provide full Speech SDK Log, as per the instructions here?
If you report an error for a specific service interaction, please report the SessionId and time (incl. timezone) of the reported incidents. The SessionId is reported in all call-backs/events you receive.
Any other additional information

Duplicate issue #1926: icrosoft.CognitiveServices.Speech.extension.audio.lib：音频文件音频流的扩展库。 - Microsoft.CognitiveServices.Speech.extension.sourcecallback.lib：音频数据源的回调扩展库。
Created: 2023-04-19T04:59:24Z
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

...icrosoft.CognitiveServices.Speech.extension.audio.lib：音频文件音频流的扩展库。


Microsoft.CognitiveServices.Speech.extension.sourcecallback.lib：音频数据源的回调扩展库。


...

Expected behavior
A clear and concise description of what you expected to happen.
Version of the Cognitive Services Speech SDK
Which version of the SDK are you using.
Platform, Operating System, and Programming Language

OS: [e.g. Windows, Linux, Android, iOS, ...] - please be specific
Hardware - x64, x86, ARM, ...
Programming language: C#, C++, Java, JavaScript, Objective-C, Python
Browser [e.g. Chrome, Safari] (if applicable) - please be specific

Additional context

Error messages, stack trace, sample code to reproduce the issue, ...
Please provide full Speech SDK Log, as per the instructions here?
If you report an error for a specific service interaction, please report the SessionId and time (incl. timezone) of the reported incidents. The SessionId is reported in all call-backs/events you receive.
Any other additional information

Closing comment (2023-04-20T21:58:50Z): Closing as a duplicate of #1925
Repository: Azure-Samples/cognitive-services-speech-sdk

Issue #1687: [JS] can I get the audio file in Real-time Speech-to-Text?
Created: 2022-10-11T09:31:07Z
i am looking for a way to get the audio file when i use
SpeechSDK.AudioConfig.fromDefaultMicrophoneInput()
,but all most answers said it should be
SpeechSDK.AudioConfig.fromStreamInput(pushStream)
so the fromStreamInput is only way in JS?
and in this official page.the Realtime Speech-to-Text use it too?

Duplicate issue #1760: @Darinzhao you can enumerate custom models endpoints logs through [Get Custom Model Endpoint Logs](https://westus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-0/operations/GetEndpointLogs), check `.values[].self` on the result.
Created: 2022-11-23T22:00:04Z
@Darinzhao you can enumerate custom models endpoints logs through [Get Custom Model Endpoint Logs](https://westus.dev.cognitive.microsoft.com/docs/services/speech-to-text-api-v3-0/operations/GetEndpointLogs), check `.values[].self` on the result.

Originally posted by @mahilleb-msft in #1742 (comment)

Closing comment (2022-11-23T23:16:23Z): Duplicate of #1687
Repository: Azure/AKS

Issue #1480: [Feature] Azure AD Workload Identity Managed AKS Addon
Created: 2020-03-09T09:25:54Z
It would be good to have built-in support for AAD Pod Identity for which we can opt-out during creation of AKS cluster.
By doing that, we could :

Assign Azure AD identities to AKS instance and automatically register them inside the cluster
Browse the Azure portal to see which Azure AD identities are available inside the cluster

Duplicate issue #1857: Support for FeatureFlag to enable OpenID Connect via K8s API
Created: 2020-09-15T11:15:55Z
What happened:
FeatureFlag support request
What you expected to happen:
Be able to use k8s api for oidc with in-cluster service accounts
How to reproduce it (as minimally and precisely as possible):
https://banzaicloud.com/blog/kubernetes-oidc/
Anything else we need to know?:
N/A

Closing comment (2021-12-10T16:33:35Z): Dup of #1480 closing.
Repository: Azure/AKS

Issue #1344: Support setting Azure tags per node pool to persist on upgrade/scale for new nodes
Created: 2019-12-05T19:31:07Z
This issue tracks the ability to define Azure resource tags in the agentPoolProfile. These tags will be set in the agent pool's model so new nodes brought into the agent pool during upgrade and scale will receive the tags at create time.

Duplicate issue #1495: [Feature] Nodepool tags
Created: 2020-03-11T10:21:47Z
Allow for user-specified Azure tags to be passed at nodepool creation time (or cluster creation time) and these will be propagated and persist across every node of the nodepool, including new scaled nodes

Closing comment (2020-03-11T15:24:11Z): Duplicate of #1344
Repository: Azure/AKS

Issue #995: Improved AKS Versioning
Created: 2019-05-22T21:03:55Z
Tracking issue for improved AKS version that includes:

Discreet roll up AKS versions not tied to Kubernetes versions
A manifest of all component versions - container insights, aks-engine, coreDNS, etc will have tracked version numbers

Users will be able to download the manifest to look at which components are at which version (helps compatibility testing)

Duplicate issue #1098: Check aks-engine and aks version
Created: 2019-07-08T16:52:58Z
Is it possible to extract aks-engine and aks release version from a managed AKS cluster metadata?

Closing comment (2019-07-08T16:56:39Z): Not at this time. Improvements in this area are tracked in #995
Repository: Azure/AKS

Issue #8: `az aks get-credentials` fails with "permission denied"
Created: 2017-10-26T09:25:48Z
There is an open issue in the azure-cli repo. Seems to happen mostly on Windows.
Azure/azure-cli#4746
You can use this to retrieve the YAML and update your kubectl config manually:
az aks get-credentials -g <resource_group> -n <name> -f -

Duplicate issue #11: az aks get-credentials does not work on Windows
Created: 2017-10-27T21:33:13Z
Running the following command on Windows (not WSL):
aks get-credentials --n myAKSCluster -g myAKSCluster

Results in the following error:
[Errno 13] Permission denied: 'C:\\Users\\nepeters\\AppData\\Local\\Temp\\tmp7e2dtbku'
Traceback (most recent call last):
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\main.py", line 36, in main
    cmd_result = APPLICATION.execute(args)
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\core\application.py", line 212, in execute
    result = expanded_arg.func(params)
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\core\commands\__init__.py", line 377, in __call__
    return self.handler(*args, **kwargs)
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\core\commands\__init__.py", line 620, in _execute_command
    reraise(*sys.exc_info())
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\six.py", line 693, in reraise
    raise value
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\core\commands\__init__.py", line 602, in _execute_command
    result = op(client, **kwargs) if client else op(**kwargs)
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\command_modules\acs\custom.py", line 1288, in aks_get_credentials
    merge_kubernetes_configurations(path, additional_file.name)
  File "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\azure\cli\command_modules\acs\custom.py", line 829, in merge_kubernetes_configurations
    with open(addition_file) as stream:
PermissionError: [Errno 13] Permission denied: 'C:\\Users\\nepeters\\AppData\\Local\\Temp\\tmp7e2dtbku'

This occurs both in both an elevated and non-elevated command prompt.

Closing comment (2017-10-28T02:56:27Z): Duplicate of #8
Repository: Azure/AKS

Issue #274: Scaling AKS cluster puts nodes in NotReady state
Created: 2018-03-27T07:30:45Z
I've got a set of clusters running in AKS. Recently I've seen that triggering a scaling operation on the cluster (on this sample cluster from 1 to 2 nodes), causes the new node to end up in NotReady state.
kubectl get nodes
NAME                       STATUS     ROLES     AGE       VERSION
aks-nodepool1-13497206-1   Ready      agent     17d       v1.9.2
aks-nodepool1-13497206-2   NotReady   agent     36m       v1.9.2

Additional info:

Cluster node size: A4 (also happening on another one I have with D5 and a few more nodes)
Location: West Europe
Reproducible: Happens intermittently.

Questions:

Are there any timeouts for a failing scaling operation?
Are there ways to say "Kill any failing or NotReady nodes, and re-try scaling"
Are there any reliable self-healing mechanisms coupled with these operations?

40 minutes of semi-downtime due to a failed node scale that happens intermittently is going to be hard to define any SLA for ;)

Duplicate issue #386: Pods marked as Not Ready and with Insufficient Storage after scaling
Created: 2018-05-24T08:45:15Z
After scaling up a AKS cluster (version 1.9.6, created on the 11th of April 2018) we found the following problems:

The new nodes are marked as "Not Ready", as it seems something related to the CIDR
The pods living in the existing nodes gets restarted every ~1h
The existing nodes gets marked as Insufficient Storage.

Our VM size is Standard_D8s_V3, this cluster was initially created with terraform, but the scaling was instructed via az aks scale cmd.
This cluster, after a day, got stuck and all the deployments were not running anymore. We kept the cluster just in case we need to debug more deeply what happened. The nodes now are not reachable, but the master is still working.

Closing comment (2018-05-28T21:22:28Z): Probably related to #274 and #102
Repository: Azure/AKS

Issue #63: docker daemon version out of date
Created: 2017-11-30T20:37:49Z
provisioning an AKS cluster with v1.8.2 nodes show that the kubelets are running Docker v1.12.6. It'd be great for them to be running 17.06.0-ce, which is minikube's underlying docker version as of v0.24.0.

Duplicate issue #723: Upgrade AKS to the Moby container run time
Created: 2018-11-16T16:29:28Z
Type: bug fix/enhancement.
See Azure feedback forum for the parent thread: https://feedback.azure.com/forums/914020-azure-kubernetes-service-aks/suggestions/34917076-increase-kubernetes-node-docker-version-to-17-05-x
This is a tracking bug on the AKS repository to track when we officially enable the latest Moby container runtime inside of AKS. As of ACS-Engine 0.25 the Moby runtime is supported.
This issue only tracks the enablement of Moby in AKS.

Closing comment (2018-11-17T02:07:40Z): Duplicate of #63
Repository: Azure/AKS

Issue #4545: [BUG] Nodes with Ubuntu2204 ImageFamily are not able to join the cluster
Created: 2024-09-17T08:47:53Z
Describe the bug
Nodes running the latest image from the Ubuntu 2204 imageFamily are not joining the cluster. I'm running on AKS with k8s version 1.28.9.
Investigation
After ssh-ing into the node, I concluded that:

Ubuntu2204 Family is not working as of 13.09.2024 (/CommunityGalleries/AKSUbuntu-38d80f77-467a-481f-a8d4-09b6d4220bd2/images/2204gen2containerd/versions/202409.13.0).
The failure is related to missing variables when invoking the following script during node initialization:
/opt/azure/containers/ensure_imds_restriction.sh .

Content of the service file for kubelet:
Environment="PRIMARY_NIC_IP=10.117.0.121"
Environment="ENABLE_IMDS_RESTRICTION="
Environment="INSERT_IMDS_RESTRICTION_RULE_TO_MANGLE_TABLE="
Switching from Ubuntu2204 to AzureLinux solved the issue
To Reproduce
Steps to reproduce the behavior:

Run AKS (all my clusters run the same 1.28.9 version)
I am running NAP to provision nodes (probably not related?)
Try adding a node using the mentioned Ubuntu2204 image

Duplicate issue #4542: [BUG] Scale out with NAP recently started failing 
Created: 2024-09-11T18:10:01Z
Describe the bug
NodeClaims created by NAP are not launching, this causes scale out to fail. Seems to be a recent regression, describing the node  claim leads to this message:
{
"error": {
"code": "MissingApiVersionParameter",
"message": "The api-version query parameter (?api-version=) is required for all requests."
}
}
To Reproduce
Repros consistently on one of our clusters, but not the other. Perhaps this regression is starting to roll out.
Create a workload that needs to add nodes and uses NAP.
You will see the following message, but the node is never added to the cluster successfully.
[Pod should schedule on: nodeclaim/default-x7kct]
kubectl describe nodeclaim  -n kube-system
RESPO...
Reason:                LaunchFailed
Status:                False
Type:                  Launched
Last Transition Time:  2024-09-11T17:44:19Z
Message:               Node not launched
Reason:                NotLaunched
Status:                False
Type:                  Ready
Last Transition Time:  2024-09-11T17:44:19Z
Message:               Node not launched
Reason:                NotLaunched
Status:                False
Type:                  Registered
Events:                    
Expected behavior
Nodes launch and scale out the workload as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

Kubernetes version 1.30.3

Closing comment (2024-09-19T20:25:05Z): I tried the mitigation - applying the fix required me to tear down and rebuild the cluster. It seemed to be working fine for 3-4 days and then I ran into a similar set of symptoms again this morning. The logs look different this time though.
NodeClaims fail with:
- lastTransitionTime: '2024-09-19T19:35:34Z'
message: Node not registered with cluster
reason: NodeNotFound
status: 'False'
type: Registered
Any ideas? Could this be related to #4545?
Repository: Azure/AKS

Issue #972: Multi-nodepool AKS cluster with ARM template
Created: 2019-05-14T09:11:00Z
What happened: 'm hitting an issue while deploying AKS cluster with multiple pools using ARM template (apiVersion 2019-02-01, type: Microsoft.ContainerService/managedClusters). Works fine for the first time, but when I try to run the same ARM template against already created AKS cluster (no change made to the ARM template) it fails with message: "{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n "code": "OperationNotAllowed",\r\n "message": "Node pool update via managed cluster not allowed. Use per nodepool operations."\r\n}"}]}"
What you expected to happen: ARM template should be applied successfully when no change was made to the cluster (the same ARM template applied more than once). Ideally ARM template should be applied successfully when there are modifications to the cluster in it.
How to reproduce it (as minimally and precisely as possible): Create ARM template type: Microsoft.ContainerService/managedClusters with more than 1 nodepool (apiVersion 2019-02-01). Deploy the ARM template at least twice without any changes to it.
Anything else we need to know?: Multiple nodepool support is in preview. Tested on 13.05.2019
Environment:

Kubernetes version (use kubectl version): 1.13.5
Size of cluster (how many worker nodes are in the cluster?): 2 node pools, 1 VM each.
General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.): Empty cluster
Others:

Cluster created by running this command:
az group deployment create --name kubernetes-01e2346b-94ed-4de1-8c97-29b26211cd83 --resource-group <> --template-file /ansible/roles/azure.aks/files/aks-arm-template.json --parameters resourceName=<> location=westeurope dnsPrefix=<> servicePrincipalClientId=<> linuxSshPublicKey=<> networkPlugin=azure serviceCidr=10.133.128.0/17 dnsServiceIP=10.133.128.4 dockerBridgeCidr=10.134.0.1/16 vnetSubnetID=<> maxPods=100 enableHttpApplicationRouting=false kubernetesVersion=1.13.5
ARM template file:
aks-arm-template.json.txt

Duplicate issue #943: Unable to use the autoscale on VMSS backed AKS.
Created: 2019-05-03T07:34:27Z
I am trying to enable the autoscale feature on a AKS that i deployed via the portal using the az CLI using the command :
az aks update --resource-group  --name  --enable-cluster-autoscaler --min-count 1 --max-count 3
I am getting the following error:
Operation failed with status: 'Bad Request'. Details: Node pool update via managed cluster not allowed. Use per nodepool operations.
I was expecting that autoscaler can be enabled with VMSS backed AKS.

Kubernetes version : 1.12.7
Size of cluster : 3

Closing comment (2019-05-16T21:25:20Z): Yes, dup of #972. A fix for this is done and will roll out next week.
Repository: Azure/AKS

Issue #2584: AKS Fails to build due to disabled feature: Microsoft.ContainerService/AutoUpgradePreview
Created: 2021-10-05T08:00:34Z
Since the release of the latest azurerm terraform provider 2.79.x the following error appears when building a new AKS cluster.
Plan: 1 to add, 0 to change, 0 to destroy.
azurerm_kubernetes_cluster.main: Creating...

Error: creating Managed Kubernetes Cluster "Example-AKS" (Resource Group "kubernetes-prod"): containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="BadRequest" Message="Feature Microsoft.ContainerService/AutoUpgradePreview is not enabled. Please see https://aka.ms/aks/previews for how to enable features."

Downgrading the azurerm provider to 2.78.0 fixes the issue.
The following MR caused the issue on the azurerm terraform provider.
@tombuildsstuff mentioned in the related issue on the azurerm terraform provider github project.
"Whilst this is a change in Terraform, unfortunately this is an AKS bug - since submitting the default value to the API shouldn't require this preview feature to be enabled (as it's marked as the default value in the API, too). We've raised this with the AKS Team on Friday, but I'd suggest opening an issue on the AKS Repository too where someone from that team should be able to take a look."

Duplicate issue #2587: Feature: AutoUpgrade Preview
Created: 2021-10-06T19:15:40Z
What happened:
When creating a cluster, I get the following error: Original Error: Code="BadRequest" Message="Feature Microsoft.ContainerService/AutoUpgradePreview is not enabled. Please see https://aka.ms/aks/previews for how to enable features." I don't want to enable it and never had this issue before. What changed?
What you expected to happen:
I expected Terraform to create my cluster in Github Actions but it failed with above error.
How to reproduce it (as minimally and precisely as possible):
I can re-run the jobs for my workflow.
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Size of cluster (how many worker nodes are in the cluster?) 3
General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.)
Others:

Closing comment (2021-10-07T20:48:16Z): Duplicate: #2584
Repository: Azure/azure-sdk-for-go

Issue #18332: Add support for parameterized SQL queries for CosmosDB
Created: 2022-06-07T21:36:25Z
Feature Request
Azure Cosmos DB supports queries with parameters.
However, ContainerClient.NewQueryItemsPager in azcosmos only supports a query string without accompanying parameters.
It would be handy to be able supply parameters to mitigate SQL injection.

Duplicate issue #18570: Missing Parameter Support for Query
Created: 2022-07-11T17:34:50Z
Feature Request
The new SDK doesn't appear to support parameters. This is a blocker for updating Dapr to the new SDK. Below is a link to the query object.

  
    
      azure-sdk-for-go/sdk/data/azcosmos/cosmos_client.go
    
    
         Line 180
      in
      9bad9e6
    
  
  
    

        
          
           Query: query,

Closing comment (2022-07-11T18:03:50Z): Looks like a dupe of #18332
Repository: Azure/azure-sdk-for-go

Issue #22475: [Key Vault] Add more samples
Created: 2024-02-28T21:24:37Z
Increase the number of samples in the Key Vault modules, including a sample for ImportKey as requested in this issue and ImportCertificate as requested in this issue.
An increase in samples will hopefully fill the documentation gap, especially helping new users unfamiliar with the Go SDK.

Duplicate issue #21873: [Key Vault] Add Samples for ImportCertificate
Created: 2023-11-02T20:38:53Z
Create samples for ImportCertificate and improve docs. When importing a PFX file, the user does not need to specify the content type. With a PEM file, they do. This currently isn't clearly documented in Go and lead to customer confusion in this issue.
Want to fix the gap in our documentation and create samples for uploading both file types.

Closing comment (2024-06-25T21:15:44Z): Duplicate of #22475
Repository: Azure/azure-sdk-for-go

Issue #19214: Support PoP token binding via Signed HTTP Request (SHR) for public client apps
Created: 2022-09-27T18:52:15Z
Intro:
Proof of Possession is intended to ensure that the client that requests a token is the only client that can use the token. This is accomplished by the client generating a key pair and requesting that the public key be included in the issued access token. The client library then generates a wrapper token signing it with the private key that is only known to it.
Proposal:

Ensure all Azure Identity SDKs are able to call into WAM (this will give RT binding on Windows, for public client). This feature is available in .NET as a preview.
Add API support for using access token binding. This requires the app developer to inform the SDK about the protected API they're about to call (i.e. what is the target URL), and to extract a nonce from 401 and 200 headers.

Duplicate issue #19260: Support token binding for public client apps
Created: 2022-10-03T22:42:00Z

Closing comment (2022-10-04T15:38:59Z): Duplicate of #19214
Repository: Azure/azure-sdk-for-go

Issue #1943: Container Registry API returns Storage Account ID in lower-case
Created: 2018-06-01T12:20:07Z
👋
Our automated tests have detected a change in the Container Registry API where the Storage Account ID field is now being returned in lower-case rather than matching the casing/format used by the Storage Accounts API (as is the convention in the rest of Azure). Specifically, when sending the value:
/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/testAccRg-2825161317986571725/providers/Microsoft.Storage/storageAccounts/testaccsaxbvj

(which is the ID returned from the Storage Accounts Service) we get back the value:
/subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/testaccrg-2825161317986571725/providers/microsoft.storage/storageaccounts/testaccsaxbvj

This is using API version 2017-10-01 in SDK v16.2.1 - and we first noticed this change on the 25th May 2018 (we're trying this in West Europe, but I assume it's a global change) if that helps correlate it in any way.
Would it be possible to fix the broken API? This is causing spurious diff's at our end
Thanks!

Duplicate issue #2181: StorageAccount id is lower case in container registry 'Classic' sku.
Created: 2018-07-04T12:18:42Z
Hi team,
We found a issue that rest api always return lower case storage account id in container registry when sku set to 'Classic'. It's not make sense and the issue from rest api level.
Reference:
https://docs.microsoft.com/zh-cn/rest/api/containerregistry/registries/get#storageaccountproperties
Thanks,
Chang

Closing comment (2018-07-04T13:03:22Z): Duplicate of #1943
Repository: Azure/azure-sdk-for-go

Issue #21078: [KeyVault] Update migration and troubleshooting guides
Created: 2023-06-28T22:54:37Z
Improve the Key Vault troubleshooting guides and link to them from the migration guides for each package.
See what .NET and Python did for reference.

Duplicate issue #19412: Add Migration guide for KeyVault packages
Created: 2022-10-24T17:51:36Z
Add migration guides for azkeys, azcerts, azsecrets

Closing comment (2024-05-29T18:16:41Z): Tracked in #21078
Repository: Azure/azure-sdk-for-go

Issue #21799: Bump to a beta version post release
Created: 2023-10-18T17:16:08Z
This ensures that if a post-release commit version of a module is used that the telemetry info shows up as a beta release.
Note that we should only use a -beta.N suffix for releases that are v1 or greater.  v0 releases should continue to bump the patch version.

Duplicate issue #21812: Packages should auto rev to -beta.1 upon release
Created: 2023-10-20T18:41:30Z
Should someone build from source we want the user-agent version to reflect an unreleased beta version and not a patch version.
The release version update should be:
e.g.
Release of 1.1.0
Auto update revs to 1.1.0-beta.1

Closing comment (2023-10-23T14:11:17Z): Dupe of #21799
Repository: Azure/azure-sdk-for-go

Issue #12452: Provide 2019-10-01 version of consumption APIs
Created: 2020-09-09T14:03:40Z
Feature Request
Atm, we see the /consumption/mgmt api calls are mapped up to 2019-01-01 https://github.com/Azure/azure-sdk-for-go/tree/master/services/consumption/mgmt.
With 2019-10-01 new improvements were added as supporting more subscription types.
Any idea when we can see this version in the sdk?

Duplicate issue #12571: Provide costmanagement version 2019-11-01 
Created: 2020-09-22T04:59:37Z
Feature Request
Please update the SDK to add cost management version, 2019-11-01  to SDK. The most latest version available is 2019-10-01

Closing comment (2020-09-27T03:21:20Z): Duplicate of #12452
Please track the progress of this new package in #12452, thanks
Repository: Azure/azure-sdk-for-go

Issue #15166: [service-bus] receiving and deferring messages
Created: 2021-07-27T21:33:12Z
There is a API restructuring that has to happen here (for instance, in track 2 SDKs receiving deferred messages is treated as a batch operation, without a callback).
Beyond that there are quality issues we need to be aware of:

(fixed) There's a bug currently in azure-service-bus-go where we can't properly retrieve deferred messages for a dead letter queue: azure-service-bus-go: #241
Another one, filed by me, (#15210) where you can't defer a message if you're in the 'defer' message handler.

Duplicate issue #15536: [service-bus] Implement ReceiveDeferredMessages
Created: 2021-09-10T21:12:37Z
We can currently defer messages using the receiver, but cannot receive deferred messages.

Closing comment (2021-09-10T21:54:58Z): Oops, duplicate of #15166. Closing this one.
Repository: Azure/azure-sdk-for-go

Issue #18578: CosmosDB: Allow running queries without Partition Key
Created: 2022-07-12T16:55:16Z
Feature Request
In PR #17657, support was added for running an CosmosDB SQL query against a single partition in CosmosDB. However, in the Data Explorer UI and in other SDKs, a query can be run without specifying a partition key, and run across the entire container.
Could this functionality be added for feature parity with the other SDKs 🙏
Thanks!

Duplicate issue #22090: Azure CosmosDB SDK for Go support cross-partition queries?
Created: 2023-12-04T09:04:53Z
Feature Request
I am using the Azure CosmosDB SDK for Go for my application, and I need to perform a cross-partition query in Cosmos DB. However, I'm not sure if the SDK supports this or how to correctly implement it.
Do we already have this feature?????

Closing comment (2023-12-04T15:05:19Z): Duplicate of #18578
Repository: Azure/bicep

Issue #788: Allow targeting multiple scopes in a single file with `targetScope`
Created: 2020-11-03T19:06:53Z
Implementation for the syntax discussed e.g.
targetScope = [
  'tenant'
  'subscription'
]

Duplicate issue #2527: targetScope doesn't appear to support arrays
Created: 2021-05-05T14:28:25Z
Bicep version
Bicep CLI version 0.3.255 (589f037)
Describe the bug
Declaring the target scope using an array not supported as per the bicep spec
Azure Policy Documentation "Azure Policy Definition deployments target either subscription or management group scopes."
To Reproduce
Add the following to a Bicep file containing a Policy Definition:
targetScope = [
  'managementGroup'
  'subscription'
]

VS Code Warning

Expected a value of type "'managementGroup' | 'resourceGroup' | 'subscription' | 'tenant'" but the provided value is of type "array".bicep(BCP033)

Additional context
Add any other context about the problem here.

Closing comment (2021-05-05T14:38:00Z): Closing as dup of #788, but we should try to take care of this sooner rather than later cc @majastrz / @shenglol FYI