Rick Brouwer

Is it an idea to perhaps use the [KEDAScalersInfo](https://github.com/kedacore/keda/pull/6330) for this to show important information (only INFO and WARNING messages)? The idea behind it is to increase the observability. Not...

Hi @tomkerkhove I was refactoring the MSSQL scaler to match the new metadata guidelines. I thought I would also nice to add the [requested](https://github.com/kedacore/keda/issues/6104) Azure workload feature. I do not...

Hi @pauldotyu! I saw that you did a lot of work for the Azure workload identity, for example with the RabbitMQ. I was refactoring the MSSQL scaler to match the...

> Let's not poke random people and wait for the group that I have mentioned please =) my sincere apologies

> I think that we could cover this with e2e test as we have an Azure subscription. Could you open a PR to the testing infra repo to spin up...

> Great!! to see the PR progressing!! I see that the E2E test failed? Can some one share the issue here? What set of things are remaining for the PR...

It only checks for pods with the status "PodRunning" or "PodSucceeded," but ignores PodPending. I think `pod.Status.Phase == corev1.PodPending` should also be checked in this line: https://github.com/kedacore/keda/blob/3a26db68ead1d96343e082bfcd158a0669880678/pkg/scaling/executor/scale_jobs.go#L264 Otherwise, it won't...

> I see the use case of this feature, but IMHO we should expose the aggregation algorithm if we allow multiple queries in the same trigger. If you check the...

In the version 2.17.1 released yesterday there are some fixes for what seems to be your issue. I wonder if your issue still occurs in version 2.17.1

Did you still get the “scaler with id 2 not found. Len = 0” message in 2.17.1?