alpacahq / alpacahq/Alpaca-API

Inconsistency with timezones

Abierto
#241 0 comentarios 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Sin datos de lenguaje
Estrellas
173
Forks
17
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**Describe the bug**
There seem to be an inconsistency concerning timezones. Different parts of the API apparently use different timezones when using timestamps.

**To Reproduce**
Steps to reproduce the behavior:
1. Request a calendar object from the api [(Link)](https://alpaca.markets/docs/api-references/broker-api/calendar/#retrieving-the-market-calendar) and look at the response.
2. Request market data and compare the timestamps (and there respective price values) of the response with market data from a third source (in my case Tradingview).

**Expected behavior**
Both responses should use the same timezone for the timestamps of their response. As you see below, apparently they don't.

**Screenshots**
![grafik](https://user-images.githubusercontent.com/16038169/199809653-0bb979d8-ec04-497d-b834-a9266da9c391.png)
The requested calendar object seem to indicate that the UTC-4 timezone is used.

![grafik](https://user-images.githubusercontent.com/16038169/199810063-ab2d8442-30c1-407f-9e24-2a1426abf154.png)
![grafik](https://user-images.githubusercontent.com/16038169/199810191-f6ae743d-56d1-4f59-85f9-d945d398c004.png)
These are charts for symbol "QQQ" on 2nd Nov 2022. Comparing the requested market data and the data from tradingview (which in my case uses UTC +1), it seems like the market data from the Alpaca API uses timestamp from timezone UTC +0. Is that correct or am i missing something?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.