Fixing 100 kilobyte max error message size #4631
Merged
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.
Tracking issue
NA
Why are the changes needed?
This
MaxErrorMessageLength
value is now used to truncateArrayNode
errors, since it was actually 100MB this resulted in potentially large FlyteWorkflow CRs.What changes were proposed in this pull request?
Correctly computing the 100KB to B conversion.
How was this patch tested?
NA
Setup process
NA
Screenshots
NA
Check all the applicable boxes
Related PRs
NA
Docs link
NA