Because it was demonstrated that data objects can come in a different receive order than they were created in FSW, the get_latest_time() method is not correct. When implemented, it was assumed that all history items would be enqueued in the same order that they were created. This is no longer a safe assumption. Effectively get_latest_time() is returns an approximation of the latest time.
I see two options to address this:
Replacing the Ram Histories in the GDS with Chronological Histories
Having the TestAPI be subscribed to all data objects and calculate latest time as items are enqueued.
Because it was demonstrated that data objects can come in a different receive order than they were created in FSW, the
get_latest_time()method is not correct. When implemented, it was assumed that all history items would be enqueued in the same order that they were created. This is no longer a safe assumption. Effectivelyget_latest_time()is returns an approximation of the latest time.I see two options to address this: