Fix CompressedDataChunk splitting#3898
Open
samirromdhani wants to merge 5 commits into
Open
Conversation
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
afa320e to
f123e7b
Compare
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com> remove unnecessary stepLengths1 assign: case split index equal to stepLengths of step Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
f123e7b to
2bba559
Compare
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
MatthieuSAUR
requested changes
May 11, 2026
Signed-off-by: Samir Romdhani <samir.romdhani_externe@rte-france.com>
|
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
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.



Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Fixes #1619
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: