Closed MrKrisKrisu closed 2 years ago
I can confirm that with the RE1 on 16.09.2021 departure at 23:35 in SSH.
The TripID of this departure is 1|214067|0|80|16092021
with lineName RE 1
.
If you want to select the trip in the station board, a trip with the same TripID is found in our database, which however has a different LineName. This is where the error that the station is not on the trip comes from. It is a different trip.
In my local environment with empty database it works.
This is the first case I know of where a TripID was assigned twice. I don't currently know how we can fix that.
One possibility would be to add lineName
to the query here. However, to do this we would need to adjust our database layout beforehand. We have a unique key on tripId
, so we can't store multiple trips with the same ID.
The error also occurs at stations in other time zones.
In London (HAFAS ID 7096001) it is not possible to check into a train. The error occurs in the function App\Http\Controllers\Controller\searchForId
.
In the beta version you can check in there. But only because there is missing the function that checks against ring lines. The bug exists there for that.
Fixed in #789
User Report via Twitter
Screenshots
Additional context See https://twitter.com/FloEllebrecht/status/1438616001289982040