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
Currently staging is acting up quite a bit (‼️ not happening on production):
Sometimes, the connection endpoint only returns the first trains of the day (e.g. at 5:30 am), even when no date parameter is set. When setting a date parameter, no results are returned. Unfortunately I don't know how to reproduce it.
Before the deployment of the new production code, staging was used for some performance testing (seeing how many days could be loaded on the small instance). This caused instability due to RAM running out, leading to the issues as in your screenshot. I've now reduced the number of days to load GTFS for to 14, meaning you can only search two weeks in the future. This should reduce the load on the server instance, while still being sufficient for testing.
Regarding the other issues, I'm still iterating quite fast on the new codebase, which lead to the development branch currently running an unstable build. This should be fixed within a couple of days
Currently staging is acting up quite a bit (‼️ not happening on production):
Sometimes, the connection endpoint only returns the first trains of the day (e.g. at 5:30 am), even when no date parameter is set. When setting a date parameter, no results are returned. Unfortunately I don't know how to reproduce it.
Every few minutes I get an
Error 504
on the connections endpoint (no other info given). e.g. https://staging.api.irail.be/connections/?lang=nl&format=json&from=BE.NMBS.008814001&to=BE.NMBS.008891702×el=departureSome vehicles give the same error as above: https://staging.api.irail.be/vehicle/?lang=nl&id=BE.NMBS.S425487&alerts=true&date=060524
Liveboard endpoint not always working: https://staging.api.irail.be/v1/liveboard/?lang=nl&station=BE.NMBS.008844628
The text was updated successfully, but these errors were encountered: