K2V indices test fail with LMDB #583

Closed
opened 2023-06-09 11:06:47 +00:00 by lx · 0 comments
Owner

Probaly due to queue_insert not being propagated soon enough, because notify occurs during transaction, and not after it has been commited. Might be fixed by adding a tx.on_commit mechanism

This will allow using LMDB for the integration test (deactivated in the next branch for now)

BTW the integration test should be ran with all the DB engines available

Probaly due to `queue_insert` not being propagated soon enough, because notify occurs during transaction, and not after it has been commited. Might be fixed by adding a `tx.on_commit` mechanism This will allow using LMDB for the integration test (deactivated in the next branch for now) BTW the integration test should be ran with all the DB engines available
lx added the
kind
wrong-behavior
label 2023-06-09 11:06:47 +00:00
lx changed title from queue_insert: ensure propagation asap to K2V indices test fail with LMDB 2023-06-09 12:33:53 +00:00
lx added this to the v0.9 milestone 2023-06-14 08:41:50 +00:00
lx closed this issue 2023-09-21 14:03:38 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Deuxfleurs/garage#583
No description provided.