Improved historical data replay with lossless tick pagination, strict incomplete-result handling, connection-loss errors, and page-level progress callbacks for ticks and time bars - #68
Draft
rundef wants to merge 4 commits into
Conversation
rundef
changed the title
rundef
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Make historical tick pagination safe across same-second boundaries.
Document coding style in AGENTS.md
Added
progress_callbackwhen requesting historical data to notify consumers of progressFail active historical requests promptly on disconnect.
Disable automatic resend for in-flight historical tick requests.
Compatibility note
get_historical_tick_data()now defaults tostrict=True; callers that intentionally accept bounded partial results should passstrict=False.