Closed it-hms closed 1 year ago
@it-hms,
There was a missing circularized event check for the string historical data EBD call.
This could have resulted in the potential loss of data when:
A fix was applied as part of a rebase operation I needed to do to resolve another bug.
Now, if there is a file circularized event, both of the red highlighted (below) method calls will result in CircularizedFileException
being thrown and the yellow highlighted (below) method call, which updates the time tracker, will not be reached.
@it-hms Was the resolution of this issue satisfactory?
yeah
The issue will be closed. Thank you for your report.
This needs to be a retry. Historical time should not be advanced so that the request is retired. There needs to be a error count.