Yogesh Jagadeesan
Yogesh Jagadeesan
We have a hosted service that uses an overridden AssemblyLoadContext to load native assemblies. One of our customers moved from Microsoft.EntityFrameworkCore.Sqlite 2.2.6 to 3.3.1. The former seemed to be using...
We have `Starting Host` log that logs the `Functions_extension_version`. Sometimes function app can fail to startup thus we may not even have that log. We need a more reliable way...
V3 and above version of functions runtime will start incrementing the minor versions for future releases. To elaborate more, releases so far have been like below ``` 3.0.15960 3.0.15828 .....
Send WorkerStatusResponse when receiving WorkerStatusRequest. Send Capability "WorkerStatus" on Init
When host sends a "WorkerStatusRequest" , the worker needs to return "WorkerStatusResponse". The latency from request to response is used for scale decisions for out-of-proc languages. Reference Java commit: https://github.com/Azure/azure-functions-java-worker/commit/fbf0e4b62a1ddcb778cf7604c425082bdb743cb5...
Send WorkerStatusResponse when receiving WorkerStatusRequest. Send Capability "WorkerStatus" on Init
When host sends a "WorkerStatusRequest" , the worker needs to return "WorkerStatusResponse". The latency from request to response is used for scale decisions for out-of-proc languages. Reference Java commit: https://github.com/Azure/azure-functions-java-worker/commit/fbf0e4b62a1ddcb778cf7604c425082bdb743cb5...
Host has a "RpcHttpBodyOnly" capability where it does not send duplicated data through gRPC. It only sends the "body" property which is either bytes or string. Reference PR: Azure/azure-functions-host#4660 Java...
### Issue describing the changes in this PR resolves #issue_for_this_pr ### Pull request checklist **IMPORTANT**: Currently, changes must be backported to the `in-proc` branch to be included in Core Tools...
Details about the issue here. https://github.com/Azure/azure-functions-host/issues/6328 The issue is not language specific. Confirmed that removing bundles, adding an eventgrid extension (2.1.0) was still causing the issue. Downgrading to 2.0.0 reverted...