It looks like you're new here. If you want to get involved, click one of these buttons!
connection was closed uncleanly (peer dropped the TCP connection without previous WebSocket closing handshake)
def on_ticks(ws, ticks)
Boys you have changed your kiteticker behaviour in the way it handles exceptions. In previous kite version if your code had any errors websocket wouldnt close it would throw error(s) and continue, here it throws an error and on_close event as well. Atleast thats my reading of the problem.
I had a code error - usage of a variable before assignment - and I ended up with kiteticker throwing this weird 1006 error. I see many guys have reported the same 1006 error which was not coming up before. You need to put up some communication or update your change log to indicate this change in behaviour else you will keep getting the same question on 1006 over and over again.
Anyway leave that.. why do you send an
on_closeevent when a new
KiteTickerconnection is made using
kws.connect(). I can see for every new connection i get back on_close event which basically has no impact on the current KiteTicker session. Is this by design that an on_close is sent for new KiteTicker connections to flush out old socket connections?
def on_ticksfunction though. Anyway I see that when a programming error (error in user code) occurs within the
def on_ticks(ws, ticks)function the web ticker sends the details of error and the also an
on_closecall back event. Ticker subsequently reconnects. Can you confirm this behavior?