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

FTW says 6 hours ago but last reading was 12:00 (now 16:00) #54

Open
BNNorman opened this issue Oct 7, 2019 · 13 comments
Open

FTW says 6 hours ago but last reading was 12:00 (now 16:00) #54

BNNorman opened this issue Oct 7, 2019 · 13 comments
Labels
bug Something isn't working

Comments

@BNNorman
Copy link

BNNorman commented Oct 7, 2019

Looking at the FTW sensor.

Data for this sensor is delayed (phone defra) so the chart always shows X hours behind. The cron job which gathers the data runs once per hour.

The odd thing is that the defra data for 12:00 today is on the system but it is 16:00 hours now. So the "time ago" ought to show 4 hours (or 5 ; DST/BST) but not 6.

@BNNorman
Copy link
Author

BNNorman commented Oct 7, 2019

It's peddling backwards - now says 8 hours ago.
I have checked the database table and s_or_r is 14:00 today as per the popup chart.
Sounds like some form of cacheing? I'm using Firefox on Windows 10
Google Chrome shows it as 3 hours ago - which is nearer the truth.
tried other browsers like opera and chromium but they just twirl the circles.

@sbrl
Copy link
Collaborator

sbrl commented Oct 8, 2019

Hrm, it definitely could be caching. It might also be a rounding error. I'll have to look into this.

Other browsers should work too. I suspect we might have a bit of a performance problem to look into as well.

@sbrl sbrl added the bug Something isn't working label Oct 8, 2019
@sbrl
Copy link
Collaborator

sbrl commented Oct 10, 2019

Found the bug! It is indeed a stray cache header, I think.

@BNNorman
Copy link
Author

Good stuff

@sbrl
Copy link
Collaborator

sbrl commented Oct 10, 2019

I've also fixed a CI bug too. Does it work on the beta version now?

I've also done the external rename, so feedback on that would be great too.

Internally I use Air Quality all over the place. The README and API documentation still uses the "Air Quality Web" name too. I need a new name to move everything to in that sense before I can go ahead with an internal rename.

@BNNorman
Copy link
Author

BNNorman commented Oct 10, 2019 via email

@sbrl
Copy link
Collaborator

sbrl commented Oct 10, 2019

Hrm, it doesn't seem to have updated. It's supposed to now show "Sensor Map", not "Air Quality Map". I'll have to look into it @BNNorman.

@BNNorman
Copy link
Author

Same here. Bloody caching

@sbrl
Copy link
Collaborator

sbrl commented Oct 11, 2019

Caching is great when it works....

This time though I'm suspicious of another CI bug :-/

@BNNorman
Copy link
Author

Rather screws dynamic content.

@sbrl
Copy link
Collaborator

sbrl commented Oct 11, 2019

...if done incorrectly.

@sbrl
Copy link
Collaborator

sbrl commented Oct 12, 2019

Ah, it is showing for me now. It's odd because the title there isn't even part of the API. It's actually part of the static index.html that is served as the entry point to the web interface. Does it work for you too? Here's what I now see:

image

@BNNorman
Copy link
Author

No, but im on my tablet watching a movie. Trying to clear history and cache. I do wish they'd leave stuff where i can find it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants