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

Woking still shows expired Disruption station message #21

Open
josh-the-tech opened this issue Nov 20, 2019 · 3 comments
Open

Woking still shows expired Disruption station message #21

josh-the-tech opened this issue Nov 20, 2019 · 3 comments
Assignees

Comments

@josh-the-tech
Copy link

Woking is still showing a disruption station message for Bournemouth, which is now fixed and is no longer showing on the National Rail Enquires app. This is causing it to display on UK Departure Boards boards that use this data source.

@peter-mount
Copy link
Owner

The problem here is that under certain circumstances I don't get the message that the Station message is now invalid - can happen in some circumstances.

I'ts a difficult issue to determine if the message is still invalid or not depending on it's age.

For this instance I've restarted the d3 service removing all station messages so that one should be gone.

I'll revisit the code to see how better to determine how long to keep them in there after they were last updated - could be similar to a previous issue in another cache, but can't reduce the life span of an entry too low else I could end up hiding valid station messages.

@mattmoo44
Copy link

I have a station message from the 12th of April still showing at Mottingham (MTG)

@josh-justjosh
Copy link

Hi there.
I've noticed that an expired station message is still showing at Derby. The one at Sandy that I mentioned here is now so old the Latest Trave News link now 404s. I did create an issue on the nre-feeds repository thinking that was the right place.

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

No branches or pull requests

4 participants