11 most recent events by user matt occurring on or after 2023-02-19 20:14:36.
More ↑
2023-02-21
| ||
16:54 | Fixed run-id issue that caused wrong db to be addressed. check-in: c2f5ef0caf user: matt tags: v1.80-tcp-inmem | |
15:40 | wip check-in: b51df9a459 user: matt tags: v1.80-tcp-inmem | |
11:39 | server start smooth, but initial data load to inmem broken. check-in: 677b6ef8e8 user: matt tags: v1.80-tcp-inmem | |
2023-02-20
| ||
20:05 | Hacky solution for no-sync db check-in: b8f2578046 user: matt tags: v1.80-tcp-inmem | |
14:17 | wip. better but now there are run-away issues in ext-tests: check-in: 94e5d1fb43 user: matt tags: v1.80-tcp-inmem | |
10:32 | wip check-in: 0ac0c8e72f user: matt tags: v1.80-tcp-inmem | |
08:35 | wip, dashboard and list-runs work check-in: 4eb82b3919 user: matt tags: v1.80-tcp-inmem | |
07:16 | Removed dbmemmod.scm check-in: 74ff6cc920 user: matt tags: v1.80-tcp-inmem | |
2023-02-19
| ||
22:01 | misc needed fixes check-in: 263e0fe253 user: matt tags: v1.80-tcp-inmem | |
21:23 | Sync back implemented, compiles but not tested check-in: c70de6806c user: matt tags: v1.80-tcp-inmem | |
20:14 | list runs now working with data sync'd from ondisk to inmem (but no last_update support). check-in: 12db00e83a user: matt tags: v1.80-tcp-inmem | |