Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Sometimes, when the security exchange timezone is not the same as the data timezone, the class
DateChangeTimeKeeper
does not produce a delisting event but theSubscriptionDataReader
thinks one was produced. Apparently, this happens since inDateChangeTimeKeeper
the date returned by_tradableDatesInDataTimeZone
is compared with the delisting date after converting it to the exchange timezone. However, inSubscriptionDataReader
, that same date is directly compared with the delisting date.Related Issue
Closes #8413
Motivation and Context
With this change all index option contracts will be exercised after being delisted
Requires Documentation Change
N/A
How Has This Been Tested?
In progress...
Types of changes
Checklist:
bug-<issue#>-<description>
orfeature-<issue#>-<description>