OBA fails with GTFS-rt feed from another OBA server

[sirott]

I've had problems with the GTFS-rt from the King County OBA server sending empty arrival info; something like:

stop_time_update{ arrival { } departure { time: 1442424141 } }

OBA throws an IllegalStateException when this happens. It should be modified to handle this gracefully and use the departure time instead (or the arrival time if the departure time is missing).

[barbeau]

Can you try the develop branch and see if this still occurs there?

As part of the per-stop prediction work we added support for arrival and departure times, which might fix this.

[sirott]

Not seeing the changes that would fix this; the problem is in GtfsRealtimeTripLibrary.computeArrivalTime where an exception is thrown which is inconsistent with returning -1 for the other cases where the arrival time info is missing.

[sheldonabrown]

@sirott do you have a pull request to fix this? I'd be happy to review it if so...