Fix division by zero error when importing happens too fast #138
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.
I was writing a very simple import profile and that seemed to happen faster than 0.005 seconds.
Because the delta gets rounded to 2 decimals, it will result as 0 seconds. When calculating how many rows/entities per seconds, the importer will end up dividing by zero. This way the calculations will be legit again, more precise and the displayed delta will now be rounded to 4 decimals instead of 2.
If you have a different opinion on this issue, please let me know!