Patch for missing tick data in history call #6932
Merged
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
This solves unmatching tick count in history calls, as described in #6929 but this is only a patch. The actual bug is in the
Slice.Get
method, which is expecting a dictionary ofSymbol->T
. In theTick
case, each slice might have multiple ticks, and it is only getting the last one in order to comply with the expected dictionary.Related Issue
Part of #6929
Might close it but it is only a patch, we would need a spin off issue or keep it open.
Motivation and Context
Requires Documentation Change
How Has This Been Tested?
Unit test and regression algorithm
Types of changes
Checklist:
bug-<issue#>-<description>
orfeature-<issue#>-<description>