Use session limit max concurrency in a limited scope #10008
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
- Only takes effect when discord provides an increased max concurrency, user has not indicated clustering at all, and before_identify_hook has not been overriden This partially addresses Rapptz#8430 This depends on a smaller change in Rapptz#10007 I cannot personally test this change.
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.
Summary
See #8430
This only applies when not clustering and when before_identify_hook has not been overridden.
This should limit the scope to bots that are slim enough to run in a single process yet large enough to have a raised max concurrency, without touching the behavior for bots that have already overridden this using the provided hook.
It's built on top of changes in #10007
Checklist