Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add cutoff for starting data on historical. #38

Open
synchronizing opened this issue Jul 1, 2019 · 0 comments
Open

Add cutoff for starting data on historical. #38

synchronizing opened this issue Jul 1, 2019 · 0 comments
Assignees
@synchronizing
Labels
🤦🏻‍♂️bug Something isn't working 🐍 python

Comments

@synchronizing
Copy link
Contributor

In some specific instances, the server responds with a timestamp before the given start data/time for historical(). It would be wise to add a cut-off in the case this issue happens.
@synchronizing synchronizing self-assigned this Jul 1, 2019
@synchronizing synchronizing added the 🤦🏻‍♂️bug Something isn't working label Jul 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@synchronizing synchronizing

Labels
🤦🏻‍♂️bug Something isn't working 🐍 python
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@synchronizing