You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(the long waiting time at the end likely just was due to bad network condition, you can ignore that)
This was recorded at 2024-12-08 23-55-27 trying to request trips at Leipzig Hbf.
Aka the most recent time did not show any trips, which obviously is most important.
It is notable this is kind of a sliding window here, at 00:12 a train departing at 22:37 was shown.
Browser console logs
N/A
Browser
Firefox for Android, also tried Traveldroid
The text was updated successfully, but these errors were encountered:
rugk
changed the title
Many timeouts, often no stations being found
Many timeouts, often no stations being found, only backwards search works kinda
Dec 8, 2024
Mir fällt dabei auch immer wieder auf, dass die Zeitspanne für die suche falsch angegeben ist. Im ersten video wird bspw keine Verbindung zwischen 23:33 und 23:33 gefunden. Das ist an sich auch ein valide Aussage. Da Stelle ich mir eher die Frage warum die Start und Ende Zeiten identisch sind.
Da Stelle ich mir eher die Frage warum die Start und Ende Zeiten identisch sind.
Das liegt daran, dass wir hier vom HAFAS ne Fehlermeldung bekommen, an die wir nicht gedacht haben. Mit #3038 haben wir jetzt zumindest mal eine Fehlermeldung eingebaut, die das etwas klarer macht. Der Text mit "Uhrzeit X bis X" bleibt zwar weiterhin, aber das ist die aktuelle Unfähigkeit, richtig mit der Abwesenheit des Backends umgehen zu können.
Ok, so the occurrence of this bug should hopefully be reduced due to the recent deployment of #3041. This will not altogether remove it but it should drastically reduce the requests to the backend and hopefully give an overall better performance.
I'll leave this issue open for a few days until we know that it's gotten better. If so, I'll close it. We won't be able to fix this completely because external dependencies are external dependencies. 🥴
Describe the bug
Yeah the interruptions are kinda known now (in German, supposedly HAFAS also has timeouts, though it is said Traewelling does not use HAFAS directly at least) but today also discovered that somehow no stations are shown after a certain time period, reproducibly.
Steps to reproduce
See video:
screen-20241208-235527.mp4
(the long waiting time at the end likely just was due to bad network condition, you can ignore that)
This was recorded at 2024-12-08 23-55-27 trying to request trips at Leipzig Hbf.
Aka the most recent time did not show any trips, which obviously is most important.
It is notable this is kind of a sliding window here, at 00:12 a train departing at 22:37 was shown.
Browser console logs
Browser
Firefox for Android, also tried Traveldroid
The text was updated successfully, but these errors were encountered: