-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Re-import] fixed SQL exception when maxPace == NaN
- Loading branch information
1 parent
ee09ccf
commit 921415c
Showing
2 changed files
with
18 additions
and
3 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
921415c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FJBDev Can you check why maxPace can be NaN which causes an SQL exception when saving a tour, this occured when I reimported a tour.
921415c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that issue occur when you reimport any tour ? or only specific tour ?
I will try to reproduce and investigate
921415c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was only this specific tour but I found other tours where maxPace is OK. I need to debug hibernate to find the troublesome field, it is not so easy to detect.
921415c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here, all my tours have a valid maxPace so there is something in your specific tour that create a NaN value.
You can send it to me if you want me to investigate.
I am surprised because the computation of MaxPace is simple in my commit
921415c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This bug occur when the none smoothing algorithm is used and
timeDiff == 0
, fixed in 60ec227