Xavier Morel 029957dbeb [IMP] *: trigger-ify task queue type crons ... These are pretty simple to convert as they are straightforward: an item is added to a work queue (table), then a cron regularly scans through the table executing the items and deleting them. That means the cron trigger can just be added on `create` and things should work out fine. There's just two wrinkles in the port_forward cron: - It can be requeued in the future, so needs a conditional trigger-ing in `write`. - It is disabled during freeze (maybe something to change), as a result triggers don't enqueue at all, so we need to immediately trigger after freeze to force the cron re-enabling it.		2024-08-02 15:14:50 +02:00
..
conftest.py	[IMP] *: trigger-ify task queue type crons	2024-08-02 15:14:50 +02:00
test_batches.py	[CHG] forwardport: perform forward porting without working copies	2024-07-08 14:37:14 +02:00
test_conflicts.py	[FIX] *: don't send merge errors to logging	2024-07-26 14:48:59 +02:00
test_limit.py	[FIX] *: don't send merge errors to logging	2024-07-26 14:48:59 +02:00
test_overrides.py	[CHG] *: move forward-porting over to batches	2024-05-24 09:08:56 +02:00
test_simple.py	[IMP] *: trigger-ify task queue type crons	2024-08-02 15:14:50 +02:00
test_updates.py	[CHG] forwardport: perform forward porting without working copies	2024-07-08 14:37:14 +02:00
test_weird.py	[IMP] *: trigger-ify task queue type crons	2024-08-02 15:14:50 +02:00