-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update to gRPC 1.66.0 #14342
base: main
Are you sure you want to change the base?
Update to gRPC 1.66.0 #14342
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,6 @@ | ||
# Unreleased | ||
- [fixed] Fixed use-after-free bug when internally formatting strings. (#14306) | ||
- [changed] Update gRPC dependency to 1.66. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should this be marked as fixing #14323? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I was on the fence about this. I personally haven't been able to verify that this fixes #14323 given that the issue is not deterministically reproducible. Based on the stack trace and @HannahShiSFB's comment, it's very likely. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My perception is that the only reasonable next step for #14323 is asking a customer to validate if 1.66.0 addresses it, so we should do so and then reinvestigate if it doesn't fix it. |
||
|
||
# 11.6.0 | ||
- [fixed] Add conditional `Sendable` conformance so `ServerTimestamp<T>` is | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're updating, why not get fully up to date with the latest 1.69