-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Dapr 1.12 #1003
Comments
Dapr maintainer and Azure Container Apps engineer here. As you can tell by the 1.12.1 and 1.12.2 patch releases in the dapr/dapr repo there were quite a few things that needed to be fixed in the 1.12.0 release as well. We are looking into ways to give customers more control over the Dapr version they are running. But until then, we are conservative about version upgrades. I think it's fair to say that the 1.12.2 release is finally looking more stable - so there is a good chance we'll be bringing that version to Container Apps in the near future. Any critical 1.11.X issues receive patch releases, and we are very fast to update Container Apps to patch releases of the same minor version. Thanks for your patience while we work to ensure the stability of the 1.12.X upgrade. |
Thanks for the additional information and looking forward to more Dapr control! The connection/memory leak was identified against 1.11 and not sure if it was backported into a 1.11.x release. Verified the connection leak is gone when using the 1.12 sidecar locally. |
We're currently targeting early January 2024 for the availability of Dapr 1.12 in ACA. |
@jsheetzmt I just read through the issue dapr/dapr#6734 - there the Dapr Runtime maintainers decided that this issue is not a leak / bug, but rather some unoptimized code which was improved in 1.12. If you feel that this is a bug / leak then I suggest opening an issue in https://github.com/dapr/dapr/ to ask for this fix to be applied in 1.11 as well (the runtime maintainers will need to decide on this). 1.10 and 1.11 are still supported releases - so should receive patch releases for issues. Once this gets included in a 1.11.X release in Dapr we can bring this change very quickly to ACA. |
Is there an update to this please? |
We have been working on this with utmost priority. Because of significant internal architectural changes in Dapr 1.12 this version upgrade has been especially difficult to bring to Container Apps. We are currently finalizing a release candidate and will perform our own internal testing. Once we are satisfied with our testing we will then get this rolled out in ACA. It will be based on Dapr 1.12.4. |
hi, any update here - we are waiting for this update |
Several people on my team have been working on this. We ran into a compatibility problem with Dapr 1.12 during the release process. We have since addressed this and are currently in the final testing phase before attempting another rollout of Dapr 1.12. I currently expect the release to occur within the next 2-3 weeks, unless other technical challenges are encountered.
|
@berndverst Any update on Dapr 1.12 rollout? |
We are currently waiting for the next internal platform feature release to be rolled out. This will include Dapr 1.12. I do not have an exact timeline unfortunately. I will provide an update here as soon as I learn of the deployment date. Hopefully soon 🤞. |
fyi I see 1.12.5 in our env already |
@lewis-hu - that's correct. Dapr 1.12.5 was rolled out as part of the updates for Microsoft Build. |
What is the ETA for Dapr 1.12? 1.12 fixes a memory leak when doing service-to-service invocation through the gRPC proxy.
dapr/dapr#6734
The text was updated successfully, but these errors were encountered: