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.

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

Compositions not always correct #518

Open
koeleboe opened this issue May 2, 2024 · 2 comments
Open

Compositions not always correct #518

koeleboe opened this issue May 2, 2024 · 2 comments

Comments

@koeleboe
Copy link

koeleboe commented May 2, 2024

For example

https://api.irail.be/v1/composition/?id=4137 says there is one 1 desiro, but the realtime nmbs says 2 desiros. There are indeed 2 desiros (i'm on it :D). Moreover, for some reason, only the part from Leuven to Mechelen is shown in the call (and not the part from Mechelen to Ghent), but this does not affect the composition.

Ic 4136 has the same issue. In real time, there is only 1 desiro, but api says 2.
Screenshot_20240502_165137_Samsung Internet

@Bertware
Copy link
Member

Bertware commented May 2, 2024

Testing locally shows the correct composition for both trains, and in both cases the source has changed as well.
Seems like the composition was updated 2024-05-02 17:01:03, cache duration should probably be decreased on compositions in order to get these updates

@koeleboe
Copy link
Author

koeleboe commented May 2, 2024

Yeah, that makes sense, but weird that the composition is updated after the train arrived at the last station.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants