Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Actual Departure Times at Origins are not in database #1

Open
grundleborg opened this issue Sep 30, 2015 · 1 comment
Open

Actual Departure Times at Origins are not in database #1

grundleborg opened this issue Sep 30, 2015 · 1 comment

Comments

@grundleborg
Copy link
Member

Seems to be some issue with the data coming down the wire from the push port - for some reason it looks like the actual departure times at origins get cleared. Either that or there's a screw up in the code that saves them to the schedule_location record row.
@grundleborg
Copy link
Member Author

Found the bug - was a silly error in the TS message processing code. I have a fix in testing - once I've verified that there are no obvious negative side effects I'll push a branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grundleborg