-
- Private work.
- Some work on difference arrays (line sweeps) and bisect, for range problems with large inputs.
- Nitrotype.
- PBs, IBORs, SEMVs, more.
- https://www.xwordinfo.com/Popular?year=2023
- Talked to multiple old colleagues.
- Updated windows and vscode.
- Some sys design, primarily in obj storage splitouts.
- Supercontest.
- Async score fetch, better logic around fetched gametime windows (vs
SCORE_DAYS), no more commit_scores on request (so a little faster too). This is huge for simplicity. Before, you’d have to determine if any codepath / logic / route required live scores or not, and fetch/commit if so. Now, it all happens in the background. The DB is kept up to date with separate logic. Then the routes just pull the data.
- https://gitlab.com/bmahlstedt/supercontest/-/issues/146
- Remember APScheduler defaults to in-memory jobstore. My app loads all jobs on start, doesn’t need history, isn’t complex for loss/reentrance/etc. So I don’t need persistence. I could just add a table in the pg db for the jobs, but not necessary.
- And remember, flask-apscheduler is by default a
BackgroundScheduler.
- On the admin page, I used to have the ability to add/remove jobs. It was unreliable (likely bc I wasn’t using a persistent jobstore, and multiple workers). Can add that back at some point.
- Upgrading stripe caused a checkout problem: https://gitlab.com/bmahlstedt/supercontest/-/issues/217
- Incorporated the new product/prices APIs.
- Installed stripe CLI in wsl2 (ubuntu). Played with it in dev.
- Banner, lines, picks.
- Confirmed that AFTER picks open, BEFORE lines are committed,
season and week are defined and passed to the query to get_games to check datetimes before score fetch, and the query results = empty list (nothing matches that week yet). But no error. All good.
- Changed line commit to be scheduled as well, rather than manual.
- https://gitlab.com/bmahlstedt/supercontest/-/issues/219
