Bug with execution of reset+shift concurrently

Issue #615 resolved
Desrever Nu created an issue

From henry's report:

I found my nubot on btccoid is running and generating logs, buy doesn't submit liquidityinfo and trade orders. Everything recover when I restart NuBot manually. But It will fail to keep submitting liquidityinfo soon, and stop submiting trade orders after 1 or 2 days. Would you have a look at it?

Thank you very much.

log file: https://raw.githubusercontent.com/henrynu/LPC/master/btcidbot/standard.html

Comments (13)

  1. Benjamin Cordes

    After a while this appears all the time: " Already shifting walls." I think the notifyPriceChanged is not called anymore, i.e. in PriceMonitor this line is not reached anymore:

    strategy.notifyPriceChanged(sellPricePEG_new, buyPricePEG_new, price, pegPriceDirection);

  2. Desrever Nu reporter

    The logs confirm your hypothesis , after 03:16:02.076 the PriceMonitorTriggerTask is not executed . Unfortunately the verbose logs are not helping us in finding why.

  3. Desrever Nu reporter

    I am analysing the logs and starting to suspect is due to a situation where strategy is resetting orders AND received a shift request from priceMonitor.

  4. Desrever Nu reporter

    Also StrategySecondaryPegUtils doesn't get executed anymore after the wallshift is initiated @ 03:14:01.023

  5. Desrever Nu reporter

    Somewhere within or after this instruction an exception happened . ApiResponse deleteOrdersResponse = Global.exchange.getTrade().clearOrders(Global.options.getPair());

    Being exchange bitcoincoid, I recently introduced changes, after finding clearOrders was buggy. This will likely prevent this issue to happen again. However, I will now try to prevent a shift and a reset happening at the same time

  6. Log in to comment