Make PauseCap/ResumeCap no-op after registration #1790
Conversation
This file contains 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
To allow cap-notify and capabilities after registration.
DarthGandalf
approved these changes
Jun 1, 2021
|
I don't know why you still didn't merge this, but is it still needed with #1859 ? |
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.
To allow cap-notify and capabilities after registration. This is part of the road to support cap-notify in znc<>server by disabling the pausing logic of capabilities if we're registered. After registration there isn't a pause for capabilities (that's a pause to allow caps like SASL to operate before completing registration).
Extracted from #1735