You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I expected that results from RESTClient.list_aggs() would return only one result per timestamp. That is what I have observed most of the time, but I've found some exceptions. Apologies if I misunderstand something and this behaviour is expected.
To Reproduce
An example with multiple results per timestamp:
Output: Counter({1664871240000: 57, 1664871180000: 14})
I.e. there 57 entries for timestamp 1664871240000, and 14 with timestamp 1664871180000.
Each entry has different attributes, i.e. different open, high, low, close etc.
Expected behavior
I would have expected a single aggregate per timestamp.
Screenshots
The text was updated successfully, but these errors were encountered:
Describe the bug
I expected that results from RESTClient.list_aggs() would return only one result per timestamp. That is what I have observed most of the time, but I've found some exceptions. Apologies if I misunderstand something and this behaviour is expected.
To Reproduce
An example with multiple results per timestamp:
Output:
Counter({1664871240000: 57, 1664871180000: 14})
I.e. there 57 entries for timestamp 1664871240000, and 14 with timestamp 1664871180000.
Each entry has different attributes, i.e. different open, high, low, close etc.
Expected behavior
I would have expected a single aggregate per timestamp.
Screenshots
The text was updated successfully, but these errors were encountered: