Closed chrisdennis closed 9 years ago
I believe this bug is applicable to the 2.0.0 version as well. Should we open a 2.0 branch for a future 2.0.1 release?
I guess the owner of one of the downstream projects would have to decide that they wanted the fix, and then request it, at which point we could think about helping them. ;)
If a update to a mapping occurs when an iterator is still live against a old table version (aged out due to resize) then the update is incorrectly propagated to the table (the mapping is removed rather than being updated to the new encoding).