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
{{ message }}
This repository was archived by the owner on Jun 16, 2026. It is now read-only.
When the summary for today doesn't exist in the database, but the server thinks it's today, then you get a page load error, it fails to finish rendering the charts and won't allow the display of summary data.
This is because the clock mis-synchronization code is suppressing the creation of new records in the summary table because, for instance, the values are larger than the EOD values from the previous day. That's of course because the MATE hasn't reset it's values to 0 yet because of the clock mismatch.
We could, of course, write in zero/null values into a record for today as soon as possible. It would still cause this to happen if you loaded the page after midnight but before the first regstatus.php call happens. Hmm... because it uses the current date/time for the query. Perhaps it should use the date/time of the most recent status update? so it'll just show yesterday until it has new stuff to show for today?
When the summary for today doesn't exist in the database, but the server thinks it's today, then you get a page load error, it fails to finish rendering the charts and won't allow the display of summary data.
This is because the clock mis-synchronization code is suppressing the creation of new records in the summary table because, for instance, the values are larger than the EOD values from the previous day. That's of course because the MATE hasn't reset it's values to 0 yet because of the clock mismatch.
We could, of course, write in zero/null values into a record for today as soon as possible. It would still cause this to happen if you loaded the page after midnight but before the first regstatus.php call happens. Hmm... because it uses the current date/time for the query. Perhaps it should use the date/time of the most recent status update? so it'll just show yesterday until it has new stuff to show for today?