-
Type: Task
-
Resolution: Done
-
Affects Version/s: None
-
Component/s: None
-
None
I have a test in my app that is randomly failing and I realized that this is happening because in some cases, the generation time that I pull from the ObjectId doesn't match the created_at that's added to the object by the timestamp module. It's off by one second.
Should I not expect these to always match? Or is this a bug?