I've been getting these pretty often the past few days when backtesting.
Its a minimized JS file that polls the server for new data. If the ticks are long, often times the script will wait for that long. Is this systematic or happens randomly.
not sure it was happening quite a bit the past few days (5 of 10?).... then today... not once
happened on my first backtest this morning; opened algo w/ 1700 lines of code pushed backtest... no mouse wheel or anything and:
I'm able to "continue" and if I do the backtest does eventually finish.
This seems to only happen when I have a large algo; 1000 lines plus open.
Happens both when on dsl or satellite (I have both) and both when VPN and not.
Has happened on every backtest this morning
When a backtest is run, we ping back to the browser at the following events
1. Portfolio info
2. End of start
3. Tick start
---- Any log statements from the user, orders etc
4. Tick end
You might not see the logs for each step but we are hitting the browser with some content. It could happen the bot execution in both init and first tick is taking awfully long time and the browser is waiting to her some response from the server.
Is this causing your backtests not to work? If you click on Continue, does everything work as expected.
its happening after stop() from what I can tell. it happens at the very end of the backtest and after I click continue the backtest is done within 2 seconds. I specifically see the issue often when backtesting the full 12h btce dataset from Dec 17 23:00 2011 to current. The elapsed time of my backtest (the first thing tick() does to the last thing stop does via time.time()) for that timeframe is 52-53 seconds, no matter when I get to the continue button.
I still get this error when backtesting the full btce dataset on 12h candles.