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

futuresChart cache messed up after second new candle #705

Open
kommander opened this issue Jul 22, 2021 · 0 comments · May be fixed by #847
Open

futuresChart cache messed up after second new candle #705

kommander opened this issue Jul 22, 2021 · 0 comments · May be fixed by #847

Comments

@kommander
Copy link

Hi, I am using futuresChart and get live data, all fine. But when I use it with limit = 2 and compare the previous candle, which is set to isFinal = true, to the one from the futuresCandles endpoint, it shows a difference. This over time creates a huge inconsistency in the cache. As if after the first candle change, the candle is set to isFinal = true too early. Any idea where to fix this?
@jinusean jinusean linked a pull request Jul 22, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixed futuresChart isFinal inacurracy jinusean/node-binance-api
1 participant
@kommander