Skip to content

Conversation

cloudygeek
Copy link
Contributor

TimeZone Bug

@cloudygeek
Copy link
Contributor Author

When your computer is in a timezone different to the exchange it was incorrectly converting. So I switched out your custom formatter to one of the built in Java ISO 8601 formatters. I tested against live Alpaca data and confirmed was returning the right date with the fix. without the fix it was not correctly providing the right time to alpaca.

@Petersoj Petersoj changed the base branch from master to dev August 5, 2021 17:05
@Petersoj
Copy link
Owner

Petersoj commented Aug 5, 2021

Looks good! Yeah Alpaca used to have a bug with the start and end timestamps when using the RFC 3339 format that would ignore the timezone in the request and serve all data based on the America/New_York timezone. Glad they fixed it finally! I'll publish a patch right now.

@Petersoj Petersoj merged commit a221b71 into Petersoj:dev Aug 5, 2021
@cloudygeek cloudygeek deleted the datetimezone-bug branch August 5, 2021 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants