[ECO-4873] Max message size fix #1947
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
maratal
force-pushed
the
fix/1945-max-message-size
branch
from
84daa5d to
0a70feb
Compare
maratal
force-pushed
the
fix/1945-max-message-size
branch
from
9c9a3d9 to
33981e8
Compare
maratal
force-pushed
the
fix/1945-max-message-size
branch
from
33981e8 to
ff1fbf6
Compare
… fix adds different default values for production/sandbox and properly propogates appropriate value to calculation sites.
…to have a dedicated PR).
maratal
force-pushed
the
fix/1945-max-message-size
branch
from
ff1fbf6 to
61758e2
Compare
umair-ably
approved these changes
Jul 18, 2024
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.
Closes #1945 and #1946
maxMessageSizewasn't properly respected across the codebase. This fix adds different default values for production/sandbox and properly propogates appropriate value to calculation sites.