[do not merge] Remove databag trimming #4645
Open
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@ ## potel-base #4645 +/- ## ============================================== - Coverage 84.99% 84.93% -0.07% ============================================== Files 158 158 Lines 15519 15495 -24 Branches 2456 2447 -9 ============================================== - Hits 13191 13160 -31 - Misses 1573 1580 +7 Partials 755 755
|
sentrivana force-pushed the ivana/potel/bump-trimming branch from 5a8898d to 4ebc62f Compare sentrivana changed the title 
sl0thentr0py approved these changes Jul 31, 2025
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.
remaining_depth,remaining_breadth)max_request_body_sizeto"always"by defaultAbout the do-not-merge: We want to dogfood this separately, after we're confident the other SDK changes are ok.
Ref #4172