Fix: zero division crashes when task realtime is 0#385
Merged
nadnein merged 2 commits intonextflow-io:devfrom May 4, 2026
Merged
Fix: zero division crashes when task realtime is 0#385nadnein merged 2 commits intonextflow-io:devfrom
nadnein merged 2 commits intonextflow-io:devfrom
Conversation
Signed-off-by: nadnein <nadjav.18@gmail.com>
Signed-off-by: nadnein <nadjav.18@gmail.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
2 participants
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.
When a Nextflow task reports
realtime = 0, two separate code paths crash withArithmeticException:Calculator.weightedAverage()divides by the sum of weights, which is 0 when all realtime values are 0 — added a norm == 0 guard returning null early.CiRecordCollector.getWeightedCI()divides by duration (= complete - start), which is 0 when both timestamps are identical — added an early return of the CI at the start timestamp.