Remove the payload limit in controller subscription client #86
Conversation
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
woswos
changed the title
woswos
force-pushed
the
increaseSubscriptionPayloadLimit20250127
branch
from
e166fc0 to
d679e22
Compare
Member
Author
|
PipelineID: 1752178 |
woswos
force-pushed
the
increaseSubscriptionPayloadLimit20250127
branch
from
7f08161 to
ca1f550
Compare
Member
Author
|
PipelineID: 1752892 |
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.
For large environments, the initial value returned for subscription APIs like
SubscribeRobotBridgesEnvironmentmight be quite large. So, this PR removes the maximum payload limit for data received from the controller to support all use cases.