Bastian Burger

@Mandur and I started to take a look at the PR. Some findings that we both had: - We could not get OTAA with IoT Central to work on our...

Moving to backlog as the test coverage that we have currently (integration tests and test using the discovery logic on each E2E run on the "legacy" endpoint) give us good...

Hello @ijardillier and @Metal-Mighty and thanks for your inputs! We were considering adding this feature, sadly it's not as straightforward as pulling in a NuGet package (yet). Since we are...

@thy09 this issue was closed as not planned. I can't reactivate the issue, can you please reopen it?

Thanks @nirga! I realized that the fix is a little bit more involved than I originally anticipated, due to the differences in the non-streaming and streaming cases. It'd probably take...

Sure. The feature would apply to how we currently use evaluation flows. We pass numbers from the main flow to our evaluation flows, on which we then base our evaluation...

> Are you using streaming (python) or ASP.NET Core Integration (C#)? Or older HTTP models? @satvu I'm not using streaming or the ASP.NET Core integration. I was using the latest...

> Does the workaround from [#10640](https://github.com/Azure/azure-functions-host/issues/10640) work? @satvu Not for me, as I am using Python (I used the C# variant only to validate that the issue occurs across languages).

@satvu I am looking for an improved status code (413), as a 500 may trigger retries on the client side for my (Python) Azure Functions and it is an expected...