Support float castable values instead of just floats (bugfix) #1658
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.
Description
The new behaviour may introduce units that produce iologs in 0 time. This causes the validation after resume to crash and burn because 0 is not a float, but an integer. This fixes the issue by allowing any value that is float castable (which is slightly more than just integers, but I see no point in being strict about the timestamp of the iolog production!)
Resolved issues
Fix: CHECKBOX-1709
Documentation
N;/A
Tests
N/A