I need to find a minimum reproducible example of this (I found this bug at the end of a bit of a marathon debugging session)
It seems to happen during tree-rebalance and in my use-case specifically when deleting a number of entries. In my use case the entries being deleted were mostly, though not exclusively, adjacent
I need to find a minimum reproducible example of this (I found this bug at the end of a bit of a marathon debugging session)
It seems to happen during tree-rebalance and in my use-case specifically when deleting a number of entries. In my use case the entries being deleted were mostly, though not exclusively, adjacent