-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix train displaying as not honored despite respecting times & stop time #8699
Conversation
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #8699 +/- ##
============================================
- Coverage 36.92% 36.90% -0.02%
Complexity 2213 2213
============================================
Files 1255 1255
Lines 114109 114119 +10
Branches 3186 3188 +2
============================================
- Hits 42135 42121 -14
- Misses 70081 70103 +22
- Partials 1893 1895 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
beeef07
to
92f11e6
Compare
92f11e6
to
17a3acc
Compare
Works fine for me. Good job ! |
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.
Lgtm, good job 👌
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.
LGTM
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.
Lgtm
The bug was caused by attempting to match the schedule constraint data with the train's arrival times at each point along its route. The first table (`trainSchedule.schedule`) contains only points with time constraints, while the second table (`trainSummary.path_item_times_final`) includes the train's arrival times for all intermediate points, including those without time constraints. So, matching the indices between the two tables doesn't work because the first table skips points that aren't constrained. front: improve complexity used to find index of schedule on path front: add unit tests - Add test for case when trainSchedule does not have a schedules array - Add test for case when no matching index is found for a schedule on the path
f4c2a00
to
4615d97
Compare
closes #8654