What happened:
During the DeepCopy operation in RHT (Replicated Hash Table), the set() function is called. However, it has been observed that when isRemoved is set to true, the copied RHTNode always retains a false value for isRemoved. This results in incorrect behavior when dealing with nodes that should have isRemoved set to true.
What you expected to happen:
The DeepCopy method should correctly handle nodes with isRemoved set to true, ensuring that the copied RHTNode maintains the correct value for isRemoved.
How to reproduce it (as minimally and precisely as possible):
The issue can be reproduced by attempting to DeepCopy an RHTNode with isRemoved set to true and observing that the copied node does not retain the isRemoved value during the operation.
Anything else we need to know?:
The DeepCopy method in RHT should be updated to address this issue and ensure that nodes with isRemoved set to true are correctly copied.
What happened: During the
DeepCopyoperation in RHT (Replicated Hash Table), theset()function is called. However, it has been observed that whenisRemovedis set to true, the copied RHTNode always retains a false value forisRemoved. This results in incorrect behavior when dealing with nodes that should haveisRemovedset to true.What you expected to happen: The
DeepCopymethod should correctly handle nodes withisRemovedset to true, ensuring that the copied RHTNode maintains the correct value forisRemoved.How to reproduce it (as minimally and precisely as possible): The issue can be reproduced by attempting to DeepCopy an RHTNode with
isRemovedset to true and observing that the copied node does not retain theisRemovedvalue during the operation.Anything else we need to know?: The
DeepCopymethod in RHT should be updated to address this issue and ensure that nodes withisRemovedset to true are correctly copied.Environment: