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.
What is the problem / what does the code in this PR do
During my investigation for straxen #596 I noticed that in rare cases hitlet splitting produces zero length rows if new peaks are not sorted by time. Given the nature of records and hitlets compared to peaks this can happen from time to time. In this PR we add an explicit sorting and raise condition if zero-length peaks are supposed to be returned after splitting as this is not a desired behavior.
Unfortunately, I do not belief that this change will solve #596.