-
Notifications
You must be signed in to change notification settings - Fork 31
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
fix: keep client default client read limit when realtime doesn't specify #631
Merged
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
This is mostly for internal purposes, where we have rate limits of 0 (read: unlimited). When 0 is received from realtime, the SDK should continue with its existing defaults.
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 12:59
Inactive
sacOO7
reviewed
Feb 1, 2024
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 13:59
Inactive
sacOO7
requested changes
Feb 1, 2024
Co-authored-by: sachin shinde <[email protected]>
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 14:15
Inactive
Co-authored-by: sachin shinde <[email protected]>
Co-authored-by: sachin shinde <[email protected]>
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 14:16
Inactive
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 19:36
Inactive
github-actions
bot
temporarily deployed
to
staging/pull/631/features
February 1, 2024 19:41
Inactive
sacOO7
force-pushed
the
connection-read-limit-unlimited
branch
from
February 1, 2024 19:43
6b6b43a
to
e85f788
Compare
sacOO7
approved these changes
Feb 1, 2024
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.
LGTM
@AndyTWF do try running the test and check if |
LGTM - nicely done 👍🏻 |
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.
This is mostly for internal purposes, where we have MaxMessageSize set to 0 (read: unlimited). When this happens, the SDK should keep whatever limit it currently has set.
Previously it was trying to set 0 which prevented anything from being read from the connection/