Document Expiry Set/Get Race

Jim Borden added a comment - 7 hours ago

I don't think this is the same issue as the other one since there is only one call to set being made here. The problem I made a fix for involved two rapid calls to set expiration.

Jay Vavachan added a comment - 5 hours ago - edited

testExpiryGreaterThanDate: Since this is not the same issue, but rather the document expiry is not set when we query for expired docs. We will mark as resolved.

Right, we expect race in document expiration and then, it is not likely to users to set expiry and immediately query for it. So I will go ahead and update the unit test to wait for a small delay before querying the expired doc. Even then we could add one liner API doc explaining same? something like document expiration setting might take a tiny delay to be updated in db? @pasin

Pasin Suriyentrakorn added a comment - 2 hours ago - edited

I'm not sure I completely understand the issue. Let's have a quick chat on Monday. Also as this is another issue so I think it's a good idea to create a new ticket for it even though we don't fix it for tracking purpose.