Combining historical data with live data issue (Fix suggestion) about binance-futures-trading-bot

[conor19w]

Nice one, yeah I noticed the issue before but just ignored it because I wasn't sure if it was happening only on some candles.
Edge Case: What If a candle close happens as we download the data, probably best to just assume this is really unlikely.

When combining the historical data I do a comparison to see if the candle is later than the previous, maybe I should check that the candle interval length is uniform with the others instead.Then I could just remove the candle if it isn't uniform, this would solve both issues I guess.

[conor19w]

After thinking further, I think your solution solves the problem entirely good work.
Either way if the candle closes or not mid download the websocket stream will have that candle so we are good to throw away the last one.

[luki009]

Exactly as you mentioned. Socket stream has current candle.. Thing is yeah scenario that in historical data you will pull closed candle is really unlikely (I even say impossible) because when candle close - new candle is formed immediately therefore socket stream has previous candle as closed .. Nearly impossible situation is that you will pull historical data in exact time of candle close on miliseconds precision. In that case it would happen that you will remove last whole candle therefore in data will be 1 candle skipped. but as was already concluded that is nearly impossible situation and I believe that new candle is formed by Binance at once with close of candle so there is no chance to get closed candle without new so you always get open candle.