Add a health check to the monitoring lamba that checks for freshness of the gdq_tweets and gdq_chats tables

JSON stored in S3 should have some type of redundancy. It is kindof just an artifact of the other services, but makes sense to not have a single copy that someone could fat-finger and delete (whoops...)

Maybe look into S3's versioning system?

In switching to dayjs, had to revert localizing UTC times to local time in reducers/gdqReducers.js:normalizeSchedule

This really needs to be fixed.

If you use the graph tooltip near the right side of the screen, it'll disappear off to the right.
Should flip around to the left side of the graph line.

Sometimes games get renamed. Should get the ids returned from the INSERT query and DROP any rows that weren't updated/touched on refresh.

https://github.com/bcongdon/gdq-stats/blob/master/src/js/actions/index.js#L29

Looks like the layout got a bit borked when I put in static values post SGDQ 2016

https://github.com/bcongdon/gdq-stats/blob/master/src/js/components/GamesTable.js#L41

Should be something like "datetime" instead of referencing moment

https://gohugo.io/

When the data is missing for a period of time, the stats combine all donations during the time span into the last minute, making a unrealistic bump in the donations per minute chart. It happened between 2:01 to 4:20 PM EST today (http://gdqstat.us/?series=2).

Hi,

Will you be supporting the tracker for AGDQ 2023 starting on January 8? Someone submitted an "issue" back in July if you were supporting SGDQ 2022 when it was happening. You replied you did not have enough time to set it up. Just wanted to put the bug in your ear for this upcoming marathon. Really do enjoy following your tracker.

Thanks!

I gitignore'd bower_components, so now they're lost to time (only in my local repo)

Should either add them as vendor libs (not super keen on this), or serve them from something like cdnjs.

Need to determine how many games have been completed, and update #oGames

The CSS is currently total spaghetti

To remove spikes, only show the bottom 99% of donations-per-minute values

Page load time is a bit high with a full week's data loaded in, adding an API route for the odometer stats might be a good way at increasing site responsiveness.

(At very least, could make the way stats are accumulated from the data more efficient)

Moving another task to rake would be nice -- would avoid needing to do the whole bundle exec ... thing entirely.

Do you plan to get the tracker up and running. I always liked using it during the marathons.