Un-hide force_key_update / initiate_key_update#2101
Merged
Conversation
9 tasks
Ralith
approved these changes
Dec 20, 2024
djc
reviewed
Dec 20, 2024
f38139d to
ac50dfe
Compare
djc
approved these changes
Dec 20, 2024
Member
|
Hmm, CI seems stuck on this one? Maybe rebase? |
Collaborator
Author
Nothing to rebase over ATM. |
auto-merge was automatically disabled
December 20, 2024 20:42
Head branch was pushed to by a user without write access
ac50dfe to
09ddf56
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #2097.
Note:initiate_key_update(the one in proto) is called from various places internally, which is the primary reason for differences in their names and comment.