text:
Tick data is not getting downloaded

I ran the live_engine.py and started the strategy but tick data is not getting downloaded.
2021-04-09 23:03:53,245 - quanttrader.gui.ui_main_window - INFO - control: start_strategy 1
Log doesnot have any info after that.
Any help on this would be great.

Hi, do you see the main window? What is the message in the command window that you ran python live_engine.py?

Many thanks for your reply.
Here is the Log message when I ran python live_engine.py in the main window. and started the OrderPerIntervalStrategy in UI.
Note: The below log is during the non market hours. but  i ran during the market hours as well and could not get the tick data.
2021-04-10 09:50:19,915 - qtlive - INFO - OrderPerIntervalStrategy initiated
2021-04-10 09:50:19,916 - qtlive - ERROR - Unable to load strategy double_moving_average_cross_strategy: No module named 'talib'
2021-04-10 09:50:19,917 - qtlive - ERROR - Unable to load strategy dual_thrust_strategy: No module named 'talib'
2021-04-10 09:50:19,918 - qtlive - INFO - MovingAverageCrossStrategy initiated
2021-04-10 09:50:20,070 - quanttrader.strategy.strategy_manager - INFO - add ESZ0 FUT GLOBEX
2021-04-10 09:50:20,070 - quanttrader.strategy.strategy_manager - INFO - add CLX0 FUT NYMEX
2021-04-10 09:50:20,207 - quanttrader.brokerage.ib_brokerage - INFO - IB connected
2021-04-10 09:50:20,211 - quanttrader.brokerage.ib_brokerage - INFO - CurrentTime: 09:50:19.000000
2021-04-10 09:50:20,211 - quanttrader.brokerage.ib_brokerage - INFO - nextValidOrderId: 1
2021-04-10 09:50:20,212 - quanttrader.brokerage.ib_brokerage - INFO - Requesting market data 0 ESZ0 FUT GLOBEX
2021-04-10 09:50:20,212 - quanttrader.brokerage.ib_brokerage - INFO - Requesting market data 2 CLX0 FUT NYMEX
2021-04-10 09:50:20,212 - quanttrader.brokerage.ib_brokerage - INFO - Account list:, DU2409885
ERROR -1 2104 Market data farm connection is OK:hfarm
2021-04-10 09:50:20,217 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:hfarm
ERROR -1 2104 Market data farm connection is OK:cashfarm
2021-04-10 09:50:20,218 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:cashfarm
ERROR -1 2104 Market data farm connection is OK:usfuture
2021-04-10 09:50:20,218 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:usfuture
ERROR -1 2104 Market data farm connection is OK:usfuture.nj
2021-04-10 09:50:20,219 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:usfuture.nj
ERROR -1 2104 Market data farm connection is OK:jfarm
2021-04-10 09:50:20,219 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:jfarm
ERROR -1 2104 Market data farm connection is OK:usfarm.nj
2021-04-10 09:50:20,219 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:usfarm.nj
ERROR -1 2104 Market data farm connection is OK:eufarm
2021-04-10 09:50:20,219 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:eufarm
ERROR -1 2104 Market data farm connection is OK:usfarm
2021-04-10 09:50:20,219 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:usfarm
ERROR -1 2104 Market data farm connection is OK:usopt
2021-04-10 09:50:20,220 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2104, Msg: Market data farm connection is OK:usopt
ERROR -1 2106 HMDS data farm connection is OK:euhmds
2021-04-10 09:50:20,220 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2106, Msg: HMDS data farm connection is OK:euhmds
ERROR -1 2106 HMDS data farm connection is OK:fundfarm
2021-04-10 09:50:20,220 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2106, Msg: HMDS data farm connection is OK:fundfarm
ERROR -1 2106 HMDS data farm connection is OK:ushmds
2021-04-10 09:50:20,220 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2106, Msg: HMDS data farm connection is OK:ushmds
ERROR -1 2158 Sec-def data farm connection is OK:secdefil
2021-04-10 09:50:20,221 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: -1, Code: 2158, Msg: Sec-def data farm connection is OK:secdefil
2021-04-10 09:50:20,226 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountCode, Value: DU2409885,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,227 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountOrGroup, Value: DU2409885,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,228 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountOrGroup, Value: DU2409885,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,228 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountOrGroup, Value: DU2409885,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,228 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountOrGroup, Value: DU2409885,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,229 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountReady, Value: true,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,229 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccountType, Value: INDIVIDUAL,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,229 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,230 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,230 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,230 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedCash-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedDividend, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedDividend-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AccruedDividend-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,231 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AvailableFunds, Value: 304202.44,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AvailableFunds-C, Value: 176102.84,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: AvailableFunds-S, Value: 128099.60,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Billable, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Billable-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Billable-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: BuyingPower, Value: 1221140.34,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,232 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CashBalance, Value: 334655.8153,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CashBalance, Value: 6838.44,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CashBalance, Value: -1624.04,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CashBalance, Value: 452834.6878,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CorporateBondValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CorporateBondValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CorporateBondValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: CorporateBondValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,233 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Currency, Value: BASE,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Currency, Value: EUR,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Currency, Value: GBP,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Currency, Value: USD,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Cushion, Value: 0.945472,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: DayTradesRemaining, Value: -1,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: DayTradesRemainingT+1, Value: -1,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: DayTradesRemainingT+2, Value: -1,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,234 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: DayTradesRemainingT+3, Value: -1,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,235 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: DayTradesRemainingT+4, Value: -1,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,253 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: EquityWithLoanValue, Value: 317561.21,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: EquityWithLoanValue-C, Value: 177321.95,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: EquityWithLoanValue-S, Value: 140239.26,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExcessLiquidity, Value: 307070.30,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExcessLiquidity-C, Value: 177321.95,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExcessLiquidity-S, Value: 129748.35,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,262 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExchangeRate, Value: 1.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExchangeRate, Value: 0.8681062,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExchangeRate, Value: 1.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: ExchangeRate, Value: 0.729501,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullAvailableFunds, Value: 304202.44,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullAvailableFunds-C, Value: 176102.84,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullAvailableFunds-S, Value: 128099.60,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullExcessLiquidity, Value: 307070.30,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullExcessLiquidity-C, Value: 177321.95,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,263 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullExcessLiquidity-S, Value: 129748.35,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullInitMarginReq, Value: 20439.93,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullInitMarginReq-C, Value: 8300.27,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullInitMarginReq-S, Value: 12139.66,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullMaintMarginReq, Value: 17709.68,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullMaintMarginReq-C, Value: 7217.62,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FullMaintMarginReq-S, Value: 10492.05,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FundValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FundValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FundValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,264 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FundValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FutureOptionValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FutureOptionValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FutureOptionValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FutureOptionValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FuturesPNL, Value: 142.62,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FuturesPNL, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FuturesPNL, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FuturesPNL, Value: 195.51,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,265 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FxCashBalance, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FxCashBalance, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FxCashBalance, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: FxCashBalance, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: GrossPositionValue, Value: 98917.17,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: GrossPositionValue-S, Value: 98917.17,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Guarantee, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Guarantee-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Guarantee-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,266 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IndianStockHaircut, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IndianStockHaircut-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IndianStockHaircut-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: InitMarginReq, Value: 20439.93,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: InitMarginReq-C, Value: 8300.27,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: InitMarginReq-S, Value: 12139.66,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IssuerOptionValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IssuerOptionValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IssuerOptionValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: IssuerOptionValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,267 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: Leverage-S, Value: 0.71,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadAvailableFunds, Value: 304202.44,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadAvailableFunds-C, Value: 176102.84,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadAvailableFunds-S, Value: 128099.60,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadExcessLiquidity, Value: 307070.30,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadExcessLiquidity-C, Value: 177321.95,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadExcessLiquidity-S, Value: 129748.35,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadInitMarginReq, Value: 20439.93,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadInitMarginReq-C, Value: 8300.27,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,268 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadInitMarginReq-S, Value: 12139.66,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadMaintMarginReq, Value: 17709.68,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadMaintMarginReq-C, Value: 7217.62,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadMaintMarginReq-S, Value: 10492.05,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: LookAheadNextChange, Value: 0,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MaintMarginReq, Value: 17709.68,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MaintMarginReq-C, Value: 7217.62,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,269 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MaintMarginReq-S, Value: 10492.05,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MoneyMarketFundValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MoneyMarketFundValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MoneyMarketFundValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MoneyMarketFundValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MutualFundValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MutualFundValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MutualFundValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: MutualFundValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NLVAndMarginInReview, Value: false,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,270 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetDividend, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetDividend, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetDividend, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetDividend, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidation, Value: 324779.98,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidation-C, Value: 184539.58,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidation-S, Value: 140240.40,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidationByCurrency, Value: 324779.9763,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidationByCurrency, Value: 6838.44,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidationByCurrency, Value: -1624.04,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,271 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidationByCurrency, Value: 439296.8875,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: NetLiquidationUncertainty, Value: 137.61,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: OptionMarketValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: OptionMarketValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: OptionMarketValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: OptionMarketValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PASharesValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PASharesValue-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PASharesValue-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PhysicalCertificateValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,272 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PhysicalCertificateValue-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PhysicalCertificateValue-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationExcess, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationExcess-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationExcess-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationMargin, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationMargin-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: PostExpirationMargin-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealCurrency, Value: BASE,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,273 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealCurrency, Value: EUR,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealCurrency, Value: GBP,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealCurrency, Value: USD,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealizedPnL, Value: -0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealizedPnL, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealizedPnL, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RealizedPnL, Value: -0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RegTEquity, Value: 140240.40,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RegTEquity-S, Value: 140240.40,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,274 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RegTMargin, Value: 4937.92,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: RegTMargin-S, Value: 4937.92,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: SMA, Value: 185255.20,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: SMA-S, Value: 185255.20,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: SegmentTitle-C, Value: UK Commodities,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: SegmentTitle-S, Value: UK Securities,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: StockMarketValue, Value: -9875.84,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: StockMarketValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,275 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: StockMarketValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: StockMarketValue, Value: -13537.80,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBillValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBillValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBillValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBillValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,276 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBondValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBondValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBondValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TBondValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashBalance, Value: 334655.8153,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashBalance, Value: 6838.44,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashBalance, Value: -1624.04,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashBalance, Value: 452834.6878,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashValue, Value: 334655.82,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,277 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashValue-C, Value: 184539.58,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalCashValue-S, Value: 150116.24,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalDebitCardPendingCharges, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalDebitCardPendingCharges-C, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TotalDebitCardPendingCharges-S, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: TradingType-S, Value: STKNOPT,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: UnrealizedPnL, Value: 15135.16,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: UnrealizedPnL, Value: 6749.48,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: UnrealizedPnL, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: UnrealizedPnL, Value: 12715.40,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,278 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: WarrantValue, Value: 0.00,  Currency: BASE, AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: WarrantValue, Value: 0.00,  Currency: EUR, AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: WarrantValue, Value: 0.00,  Currency: GBP, AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: WarrantValue, Value: 0.00,  Currency: USD, AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountValue. Key: WhatIfPMEnabled, Value: true,  Currency: , AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdatePortfolio. Symbol: IBDE30, SecType: CFD, Exchange: , Position: 3.0, MarketPrice: 15261.1796875, MarketValue: 45783.54, AverageCost: 13011.35333335, UnrealizedPNL: 6749.48, RealizedPNL: 0.0, AccountName: DU2409885
2021-04-10 09:50:20,279 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 07:19
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdatePortfolio. Symbol: IBUS30, SecType: CFD, Exchange: , Position: 2.0, MarketPrice: 33787.71875, MarketValue: 67575.44, AverageCost: 27146.78725, UnrealizedPNL: 13281.86, RealizedPNL: 0.0, AccountName: DU2409885
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 07:19
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdatePortfolio. Symbol: TSLA, SecType: STK, Exchange: , Position: -20.0, MarketPrice: 676.89001465, MarketValue: -13537.8, AverageCost: 673.896445, UnrealizedPNL: -59.87, RealizedPNL: -0.0, AccountName: DU2409885
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 07:19
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdatePortfolio. Symbol: YM, SecType: FUT, Exchange: , Position: -1.0, MarketPrice: 33642.8984375, MarketValue: -168214.49, AverageCost: 167707.9, UnrealizedPNL: -506.59, RealizedPNL: 0.0, AccountName: DU2409885
2021-04-10 09:50:20,280 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 07:19
2021-04-10 09:50:20,281 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 07:19
2021-04-10 09:50:20,281 - quanttrader.brokerage.ib_brokerage - INFO - AccountDownloadEnd. Account: DU2409885
2021-04-10 09:50:20,307 - quanttrader.gui.ui_account_window - INFO - account id recorded:
ERROR 1 200 No security definition has been found for the request
2021-04-10 09:50:20,443 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: 1, Code: 200, Msg: No security definition has been found for the request
ERROR 0 200 No security definition has been found for the request
2021-04-10 09:50:20,444 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: 0, Code: 200, Msg: No security definition has been found for the request
ERROR 3 200 No security definition has been found for the request
2021-04-10 09:50:20,444 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: 3, Code: 200, Msg: No security definition has been found for the request
ERROR 2 200 No security definition has been found for the request
2021-04-10 09:50:20,444 - quanttrader.brokerage.ib_brokerage - ERROR - Error. id: 2, Code: 200, Msg: No security definition has been found for the request
2021-04-10 09:52:18,041 - quanttrader.brokerage.ib_brokerage - INFO - UpdateAccountTime. Time: 09:52
2021-04-10 09:53:12,023 - quanttrader.gui.ui_main_window - INFO - control: start_strategy 1

Hi selvanponraj,
I hope you don't mind I just deleted your post because it contains your private information.
I can see you successfully connected to ib and ib sent you back your account and stock holdings. The log file should at least record this information. Can you confirm the log only showed up in the command window but NOT in the log file?
In the folder there is config_live.yaml file, the futures have expired, can you update the files and try again? (maybe also delete the moving average and dual thrust from the config because you are missing talib package which we can address later).
Maybe send me your run results to letian dot zj at gmail dot com instead. Thanks.

Hi Letian,
Many Thanks.

Log is showing in both command window and log file.
Updated the config_live.yaml for active futures.

Sent log file to your email. please check it.
Many Thanks

Tick_data is getting downloaded by making the above advised changes.

authors: letianzj selvanponraj

repo: letianzj/quanttrader


text:
Handle io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer

Environment

Lettuce version(s): [5.0.5.RELEASE]
Redis version: [spring-data-redis.2.0.11.RELEASE]

Hello, I have an exception when I use spring-boot-starter-data-redis:
Servlet.service() for servlet [dispatcherServlet] in context with path [] threw exception [Request processing failed; nested exception is org.springframework.data.redis.RedisSystemException: Redis exception; nested exception is io.lettuce.core.RedisException: io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer] with root cause.
Is there any solution?

There's nothing we can do from our side. This is a network issue, see https://stackoverflow.com/questions/1434451/what-does-connection-reset-by-peer-mean.

If connection was lost,why Lettuce did't try to reconnect to Redis ?

i had the same problem and the problem was not in lettuce, but with my load balancer.
My load balancer was dropping tcp connection information between host and redis after certain idle time.
In my case i had two options.

Turn on keepalive in lettuce socket options and host OS needed to have valid tcp keep alive related values. https://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/
Set tcp-keepalive config in redis.conf to a shorter value. My load balancer's idle timeout was 120, so i set tcp-keepalive to 60 and it worked without problem

If connection was lost,why Lettuce did't try to reconnect to Redis ?

+1

If connection was lost,why Lettuce did't try to reconnect to Redis ?

+1

source: gharchive/issue

repo: lettuce-io/lettuce-core

license_type: permissive

license_source: bigquery


text:
CompiledBindings.WPF package reference breaks CsWin32

(I'm unsure whether to file this here, or over at https://github.com/microsoft/CsWin32/)
Something about the build process is incompatible with the CsWin32 project (and perhaps other source generators as well?).
To reproduce,

create an empty .NET 9 WPF app.
modify WpfApp1.csproj as follows:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net9.0-windows</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <UseWPF>true</UseWPF>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.Windows.CsWin32" Version="0.3.106">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
  </ItemGroup>

</Project>

I.e., add that one package reference.

modify MainWindow.xaml.cs as follows:

using System.Windows;
using System.Windows.Interop;

namespace WpfApp1
{
    /// <summary>
    /// Interaction logic for MainWindow.xaml
    /// </summary>
    public partial class MainWindow : Window
    {
        public MainWindow()
        {
            InitializeComponent();
        }

        public void SetAsForegroundWindow()
        {
            // handle focus https://stackoverflow.com/a/75705911
            if (PresentationSource.FromVisual(this) is HwndSource hwndSource)
                _ = Windows.Win32.PInvoke.SetForegroundWindow((Windows.Win32.Foundation.HWND)hwndSource.Handle);
        }
    }
}

I.e., add that one method. It's just a dummy method that calls code generated by the Microsoft.Windows.CsWin32 dependency.

add a file NativeMethods.txt:

SetForegroundWindow

do a clean build. This will work.
now, modify WpfApp1.csproj again:

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net9.0-windows</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <UseWPF>true</UseWPF>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="CompiledBindings.WPF" Version="1.0.18"/>
    <PackageReference Include="Microsoft.Windows.CsWin32" Version="0.3.106">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
  </ItemGroup>

</Project>

I.e., add this project as a package reference.

do another clean build. Suddenly, we get build errors:

1>C:\Users\chucker\source\repos\temp\WpfApp1\NativeMethods.txt(1,1,1,20): warning PInvoke001: Method, type or constant "SetForegroundWindow" not found
1>C:\Users\chucker\source\repos\temp\WpfApp1\MainWindow.xaml.cs(20,21,20,28): error CS0103: The name 'Windows' does not exist in the current context
1>C:\Users\chucker\source\repos\temp\WpfApp1\MainWindow.xaml.cs(20,64,20,71): error CS0246: The type or namespace name 'Windows' could not be found (are you missing a using directive or an assembly reference?)
1>Done building project "WpfApp1.csproj" -- FAILED.

Is there something special I can do to make this combination work?

I work on the solution to this problem

authors: chucker levitali

repo: levitali/CompiledBindings

license: MIT

license_source: github-api


text:
Broken in 1.15.1?

I can't get the theme to show in the selector since upgrading to 1.15.1.
I've installed a fresh copy of the theme with no luck.

I got the theme working by renaming nightly.css to nightly.css.old and then renaming feedly.css to nightly.css...
Then I saw I was running 1.15.1. Upgraded to 1.15.3 and all my problems went away. feedly.css is working properly again.

repo: levito/tt-rss-feedly-theme


text:
def.h: Use extern even for static

This fixes static-linking with another library on a machine running gcc-10
(untested on Windows)
See: https://git.pleroma.social/pleroma/elixir-libraries/fast_html/-/issues/8

apply PR #66 before, without your patch. Everything should be fine (tested on windows and linux, static and shared lib, with or without submodules)

@lanodan
Thanks for the report/PR. I will try to fix this soon.

@lanodan
Thanks!

source: gharchive/pull-request

authors: lanodan lexborisov vtorri

repo: lexbor/lexbor


text:
Fix PathFinder returning the same operation multiple times

When there are multiple servers with the same relative path, the PathFinder returns the same operation multiple times. This has the downside, that validation errors are no longer explained and a generic exception is thrown:
The given request matched these operations: [/example,post],[/example,post],[example,post]. However, it matched not a single schema of theirs.

This PR fixes this and ensures that every path is returned only once.

@lezhnev74 I think these changes are safe as soon as we stop strictly validating host

Hm, I am not sure I follow your insight. Can you point at the host validation part?
I see this comment which states that host is not validated: "schema://hostname" should not be included in the validation process (assume any hostname matches)

prior #33 every full server url with operation was checked, so they were different and all matches should be collected and all were important. Since we stop tracking hostname part - we can stop further matching for server list as soon as we got at least single match

So this one is good to be merged. Does it any extra contribution, or consideration?

Not sure, what are you asking about, but it fixes a bug and is ready to go IMO

authors: digilist lezhnev74 scaytrase


text:
🛑 Acceso Clientes is down

In ff78b6b, Acceso Clientes (https://intranet.samsa.com.ar/apex/f?p=1000) was down:

HTTP code: 503
Response time: 181 ms

Resolved: Acceso Clientes is back up in e7568a9 after 1 day, 5 minutes.

repo: lgimenezdev/samsanet


text:
Feature/add missing messages

This PR adds messages which are intended to represent the following objects in the LGSVL Data interface:

CanBusData
DetectedRadarObject and DetectedRadarObjectData
VehicleControlData
VehicleStateData

I did my best to interpret the enum values from other locations in the code. Please let me know if I made any errors.
In addition, please let me know if there are any fields which will be populated with fixed values in the  simulator or other fields which are AD-stack-specific. I want these messages to represent only the data that are available in the simulator. An "interface" node can then interpret them within the specific AD stack to any message type they like. This helps to de-couple the simulator from the AD stack.

@JWhitleyWork we will look into these and let you know if we see any issues. We will also need to add the messages to the simulator as well before these can be used by the simulator. Thanks!

Simulator side of this is done and will be public soon. Closing.

Thank you, @hadiTab!

authors: JWhitleyWork hadiTab


text:
Jiggle and tip work smoothly only on front, jitter when applied to the back of the card

This is the perfect lib for my use case in a production app, where my card(s) have dual animation - the same card can jiggle, as well as flip depending on based on a condition/state.
Unfortunately, after implementing CardFlip I realised that jiggle (and tip as well) only work well on the front face of the card. If we apply jiggle/tip to the back of the card, it jitters heavily (and on web, simply fails to execute the animation).
To repro, try this:
import React from 'react';
import {
  TouchableOpacity,
  StyleSheet,
  View,
  Text,
} from 'react-native';

import CardFlip from 'react-native-card-flip';

const App = (props) => {
  return (
    <View style={styles.container}>
      <CardFlip style={styles.cardContainer} ref={card => (this.card = card)}>
        <TouchableOpacity
          activeOpacity={1}
          style={[styles.card, styles.card1]}
          onPress={() => this.card.flip()}>
          <Text style={styles.label}>AB</Text>
        </TouchableOpacity>
        <TouchableOpacity
          activeOpacity={1}
          style={[styles.card, styles.card2]}
          onPress={() => this.card.jiggle()}>
          <Text style={styles.label}>CD</Text>
        </TouchableOpacity>
      </CardFlip>
    </View>
  );
};

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  cardContainer: {
    width: 320,
    height: 470,
  },
  card: {
    width: 320,
    height: 470,
    backgroundColor: '#FE474C',
    borderRadius: 5,
    shadowColor: 'rgba(0,0,0,0.5)',
    shadowOffset: {
      width: 0,
      height: 1,
    },
    shadowOpacity: 0.5,
  },
  card1: {
    backgroundColor: '#FE474C',
  },
  card2: {
    backgroundColor: '#FEB12C',
  },
  label: {
    lineHeight: 470,
    textAlign: 'center',
    fontSize: 55,
    fontFamily: 'System',
    color: '#ffffff',
    backgroundColor: 'transparent',
  },
});

export default App;

Any suggestions ?

Anything ?

repo: lhandel/react-native-card-flip


text:
Correct errors & bugs in norm_layer*

Description
This PR correct the following errors in the norm_layer*

Uniformize parameter initialization across c++ and cuda versions

Call the set_cap_factor_update update in the cuda version

Correct a typo in batchnorm2d_fwd_mean_var_cuda()

Remove the epistemic variance term from the normalization std

Correct an error in the forward's variance calculation

See the working document for theoretical details about the corrections made.
Changes Made

For both the c++ and cuda versions, the weight parameters are now initialized as float scale = 1.0f / this->num_weights;
Add this->set_cap_factor_udapte(batch_size); in the norm_layer_cuda.cu for both the Batch- and Layer-Normalization.
In batchnorm2d_fwd_mean_var_cuda(), the following typo was corrected: tmp_mu_ra_2 = tmp_mu_ra * tmp_mu_a -> tmp_mu_ra_2 = tmp_mu_ra * tmp_mu_ra
The epistemic variance term has been removed from the variance calculations as well as from the input and outputs
The formulation for the forward's variance calculations have been updated with the new one available in the working document.

Note for Reviewers
Although the corrections mentioned above are required from a theoretical standpoint, they are not solving the performance issues observed for the resnet18 applied on Cifar10.
I have tested the changes proposed on CPU & CPU using the classification.py MNIST benchmark with the FNN_LAYERNORM and FNN_BATCHNORM architectures. One thing I noted on that benchmark is that layer-normalization is working properly for both CPU and GPU. On the other hand batch-normalization works properly on CPU but fails to learn (i.e., error = ~90%) on GPU. I suspect that this is cause by a bug in batch-normalization but I have not been able to pinpoint the source yet.

@lhnguyen102 Thank you for the review. I have already implemented the changes requested and I will fully test the changes tomorrow morning and let you know if everything is all good.

@jamesgoulet thank you! look forward to testing it on my side

@lhnguyen102 I was able to test all the new changes. It is ready to merge whenever you are ready.

@jamesgoulet you had the memory leak. Here is the command I've used for memory checks compute-sanitizer --tool memcheck build/main test_fc_mnist
CUDA Runtime Error at: /home/ha/Tagi/cuTAGI/src/data_struct_cuda.cu:438
unspecified launch failure
========= Target application returned an error
========= ERROR SUMMARY: 40 errors

You also have the memory leak in CPU as well. Here is the command I used valgrind build/main test_fc_mnist
==40624== LEAK SUMMARY:
==40624==    definitely lost: 221,336 bytes in 56 blocks
==40624==    indirectly lost: 1,230,720 bytes in 12 blocks
==40624==      possibly lost: 411,352 bytes in 7 blocks
==40624==    still reachable: 224,851,996 bytes in 169 blocks
==40624==         suppressed: 0 bytes in 0 blocks
==40624== Rerun with --leak-check=full to see details of leaked memory
==40624==
==40624== For lists of detected and suppressed errors, rerun with: -s
==40624== ERROR SUMMARY: 522 errors from 3 contexts (suppressed: 0 from 0)

I think the issue is from the previous PR and the issue comes from BatchNorm. I'll work on fixing that bug

@jamesgoulet the issue comes from my test...your modifications do not cause the memory leak isue. Just push the fix for the test. All is good now.


text:
[rewrite] handle fragmented attrs and children

Handle fragmented attributes so that there is no need for end-users to depend on merging libraries.

This is redundant. You don't need libraries, just JS:
m("div", {...a, ...b, c: 'd'});

Which effectively does:
m("div", Object.assign({}, a, b, {c: 'd'}));

This PR would extend the API surface area to provide features that are (or will be if you are a no-babel using caveman 😄) build into the language itself.

I'm a no-babel using caveman :wave:

Will it be better to use polyfill of isArray as same as MDN?
Ref: Array.isArray

The polyfill isn't necessary: IE 9, the new baseline, already supports it
natively by default.
On Mon, Nov 21, 2016, 07:12 cybai notifications@github.com wrote:

Will it be better to use polyfill of isArray as same as MDN?
Ref: Array.isArray
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/isArray
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lhorie/mithril.js/pull/1416#issuecomment-261920986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AERrBPuIEIGX2HBbv7Dkk9n_8Gtu90H_ks5rAYrLgaJpZM4K3-8e
.

I think this is unnecessary, given there's already a plethora of alternatives that do the same thing (Object.assign, _.assign, $.extend, R.merge, object spread operator proposal in stage 3, etc...)
Another problem I spotted is that the refactoring introduced in this PR makes m() almost twice as slow as it is now

@lhorie how are you running benchmarks on the code? from just running the test i didn't see any difference in performance, sometimes even executed faster then previously.

You can see the difference by doing something like this:
console.time()
for (var i = 0; i < 10000; i++) {
  m("div", {class: "a"}, "b") // you can try with different variations
}
console.timeEnd()

Were you running the entire test suite via npm test? It does a lot of async things (and that's why it takes a few seconds). Those other tests dwarf the hyperscript test times by a few orders of magnitude.

authors: CYBAI SamuelTilly darsain isiahmeadows lhorie


text:
Understanding render.mouse and Render.lookAt

@liabru , I have watched the Cars example and have got pretty much good understanding of adding mouse constraints . (Thanks for nice example)
However, I don't understand following lines of code :
// keep the mouse in sync with rendering
    render.mouse = mouse;

    // fit the render viewport to the scene
    Render.lookAt(render, {
        min: { x: 0, y: 0 },
        max: { x: 800, y: 600 }
    });

I have also seen official documentation but I'm unable to get clear idea what these lines do.
Removing those lines had no effect on output.
Please someone explain.
Thanks.

I'm not sure what render.mouse = mouse; does, but I do know that the Render.lookAt() call basically sets the position of the camera, from what coordinate to what other coordinate is visible on the canvas

@LeotomasMC  thanks for your help :)
I experimented a bit with Render.lookAt() . now I understand it.
render.mouse= mouse;  is still a mystery ~

i think i also found what render.mouse = mouse is for.
the Renderer has an option to show the mouse position, and i think this gives the Renderer a mouse object from which to get the mouse position from, however, enabling this option causes the following error:
Uncaught TypeError: Cannot read property 'x' of undefined
I am assuming this is because the Matter.Mouse class actually doesn't have a Mouse.position property, and in fact, only has methods, as seen in the docs here. So I think in the end, functionally, it does nothing, but I also think that it was for rendering the mouse, which none of the examples even try to do anyway.

Thanks for looking into it @LeotomasMC - the render.mouse = mouse line is used to keep the mouse in sync with the render bounds. If the bounds are always equal to the canvas size then you won't need that, it's really only needed when the bounds size is changed e.g. for a zooming effect. You can see that in the views example by scrolling on the canvas.

authors: LeotomasMC Omkar76 liabru

repo: liabru/matter-js

license: mit


text:
Performance improvement for static or sleeping bodies.

Loop only non-static/non-sleeping bodies 8 times instead of all bodies. At the cost of one extra loop in Engine.update. Estimate is improved performance when >12% of bodies is sleeping or static.

From what I understand from the documentation https://brm.io/matter-js/docs/classes/Body.html#property_isSleeping static bodies can be threaded as if sleeping and vice versa. In this case further optimizations are possible such as:

Sleeping.update function.
Only one array to track either sleeping or static bodies (instead of one for each) in Engine.update.
Also several check in the loops of the methods that get bodies passed as parameter can be improved.


text:
pin header view

pin header view，header view出现之后不随主体滑动

快速滑动时情况未处理，会出现问题。

repo: liaohuqiu/android-Ultra-Pull-To-Refresh


text:
Split monorepo

At some point we'll have more than one top-level service in the monorepo. @kevinrutherford wanted to set a time limit before we split into independent repositories (and hence builds).

Nothing to split at the moment.

repo: libero/prc


text:
TmxMapLoader throws NullPointerException when using HeadlessApplication

Issue details
TmxMapLoader throws NullPointerException when using HeadlessApplication
Reproduction steps/code
Create a Headless application:
final HeadlessApplicationConfiguration config = new HeadlessApplicationConfiguration();
new HeadlessApplication(new RoboRallyApp(), config);

Then load a tmx map:
new TmxMapLoader().load("Maps/map.tmx");

Version of LibGDX and/or relevant dependencies
1.9.14 for all libgdx dependencies.
Stacktrace
java.lang.NullPointerException
	at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:142)
	at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:122)
	at com.badlogic.gdx.graphics.Texture.<init>(Texture.java:118)
	at com.badlogic.gdx.maps.tiled.TmxMapLoader.load(TmxMapLoader.java:76)
	at com.badlogic.gdx.maps.tiled.TmxMapLoader.load(TmxMapLoader.java:59)
	at RoboRally.Game.Board.BoardTest.createBoard(BoardTest.java:32)	<-- loads the tmx map

Please select the affected platforms

[ ] Android
[ ] iOS
[ ] HTML/GWT
[x] Windows
[ ] Linux
[ ] MacOS

TmxMapLoader tries to load the tile map's textures internally. That fails, because the headless backend doesn't offer a (Mock)OpenGL implementation. The simplest way to fix this is to just mock Gdx.gl yourself with Mockito or something similar. See here for an example.

repo: libgdx/libgdx


text:
Remove of static temporaries in math classes

With this PR I want to revive an issue previously discussed in e.g. #846. It's one step towards thread safety in the math classes.
There are still some static temporaries left: Vector3.tmpMat and Matrix4.quat/quat2. The long-lived deprecated Matrix4.tmp could now be removed.
I've run a couple of tests to verify my changes, but as far as I've seen not all modified functions are covered by them. Also, I've only run the tests on desktop systems. That said, a code review and some tests on Android/iOS would be wise. ;) Also, feel free to try the changes with your project if you are heavily using Matrix4/Quaternion.

Using varargs instead of array might cause an additional allocation, which we really want to avoid in these frequently called methods. Better move the allocation to the caller (e.g. mul(val, new float[] { a, b, etc.})) or add an additional signature which takes all the float as argument (e.g. mul(float[], float, float, float, float, etc.))

@xoppa you are right about the allocation, I wasn't aware of that. Indeed the byte code shows newarray instructions. This of course limits the usefulness of my changes. It can be easily fixed for Matrix3, but for Matrix4 it probably needs a second native mul() function to avoid the allocation.

Yeah, I'm not sure this actually solves an issue now. I guess this PR is about whether we want to complicate code for thread safety.

I don't want to complicate code for thread safety.

I'm ok with that. Let me close this PR then.

authors: MobiDevelop code-disaster xoppa


text:
allow redundant quant table in jbrd

See https://github.com/libjxl/libjxl/issues/346
This changes the behavior of jbrd so that if there are quantization tables that are not actually used (so the jxl codestream will not actually contain the values), it does not throw an error but it assumes that the unused table is exactly equal to the previous table. At encode time it checks if this is true, at decode time it is assumed that it is true.
The spec (18181-2) is a bit vague on this — it only says

Qk are corresponding quantization factors from the codestream (see ISO/IEC 18181-1 / C.6.2)

but it's not really clarified/specified what exactly "corresponding" means here. We could clarify/extend the spec later, and specify what a decoder is supposed to do when there are no "corresponding" quantization factors.
Since there do seem to be JPEGs in the wild that do have a redundant quantization table, and it always seems to be just a duplication of the chroma quant table, I think it's worthwhile to interpret the spec a bit freely here and consider "corresponding" to mean "corresponding to what's in the jxl codestream if it is used, identical to the previous QuantTable otherwise".

@deymo : I'm using clang-format-11, which sometimes does things differently than clang-format-7, 8 or 9, causing the format check to fail. Would it be possible to add versions 10 and 11 of clang-format?

@deymo : I'm using clang-format-11, which sometimes does things differently than clang-format-7, 8 or 9, causing the format check to fail. Would it be possible to add versions 10 and 11 of clang-format?

https://github.com/libjxl/libjxl/pull/401

You should re-run a workflow in order to allow merging this PR. You have to hurry up, though, because according to that page you've got 30 days after the initial run to do that!

I've noticed that re-running workflows didn't help. Maybe it's because those workflows are from before clang-format commit? Try creating an empty commit (git commit --allow-empty -m "trigger workflows"; git push) and let's see if it works.

or just rebase the change and reupload.

or just rebase the change and reupload.

Ok, I didn't think of it. That actually might be better solution.

This makes lossless jpeg recompression work on jpegs produced by various digital cameras where it previously didn't work. Worth adding into v0.6 imo.

Rebased, please re-approve.

I think that this PR deserves the newly created "spec" label. @jonsneyers WDYT?

Indeed should be clarified in part 2 of the spec how to interpret "corresponding" in this case.

authors: deymo jonsneyers ziemek99

repo: libjxl/libjxl


text:
plotting without X-server

related to https://stackoverflow.com/questions/4931376/generating-matplotlib-graphs-without-a-running-x-server
matplotlib (and ggplotd) allow drawing graphs without an X-server running (or when X-server would be too slow, eg on a network)
would be nice to allow configuring the backend, just as is done in matplotlib.
Also, putting things in static this isn't the most flexible in case user wants to set the backend based on custom logic; how about at the very least having a version(dcv_disable_static_glfwinit) which will disable the static this call to glfwInit and let the user call whatever's inside that static this manually; he can select the backend here.

all plotting code would probably be best put in a separate git repo

would be nice to have an abstraction layer that allows swapping in different plotting backends (eg with or without X-server, and also with alternatives to ggplotd) while allowing client code to use same API's.

I've had good experience with plotting images in D using SFML (i had used SWIG bindings but there's also https://code.dlang.org/packages/dsfml) ; eg allows direct and fast opengl drawing including animations with high FPS. Curious what are your thoughts on this and how it would compare to current option (eg in terms of flexibility of using arbitrary opengl, speed etc)

This sounds awesome, but it also sounds like a lot of work for dcv. But anyway, I agree it should be done.

authors: ljubobratovicrelja timotheecour

repo: libmir/dcv


text:
Hard-lock external CI actions

This PR will hard-lock external CI actions, so as to prevent any significant breakages from any updates.

Codecov Report

Merging #12 (537ce7b) into master (e32d462) will decrease coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
- Coverage   85.45%   85.24%   -0.22%
==========================================
  Files          32       32
  Lines        6918     6918
==========================================
- Hits         5912     5897      -15
- Misses       1006     1021      +15

Impacted Files
Coverage Δ

source/mir/ion/internal/stage2.d
58.13% <0.00%> (-15.12%)
:arrow_down:

source/mir/ion/internal/stage1.d
93.24% <0.00%> (-2.71%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e32d462...537ce7b. Read the comment docs.

repo: libmir/mir-ion


text:
tests do not compile

error[E0061]: this function takes 1 argument but 0 arguments were supplied
--> src/mutimpls.rs:41:40
|
41  |                 self.index = self.data.hashsort_indexed();
|                                        ^^^^^^^^^^^^^^^^-- an argument of type &mut _ is missing
|

Sorry about that. This was caused by a change in indxvec dependency. I have now issued a new version: Sets v1.2.0, which is fully compatible with the latest indxvec. However, it does introduce corresponding different usage of three methods. Please read the description in release notes at the bottom of the Readme file.

authors: jean-pierreBoth liborty

repo: liborty/sets


text:
Change from ipfs to p2p protocol

https://github.com/multiformats/js-multiaddr/pull/76 changed the
default protocol from ipfs to p2p.
js-multiaddr is a transitive dependency of peer-info, so in order
to get this change, we had to bump the version of peer-info.

The same change should probably be applied to all the other examples as well. However, I realized that some of them don't have a package.json. Adding that in order to test every example would kind of out of scope :D
Should I change the other examples as part of this PR as well even if I cannot fully test them?

I've addresses the points you mentioned, let's see if I broke anything :see_no_evil:


text:
[Bug] [move-prover] Type-checking and using len(v) in the specification language.

🐛 Bug
In verifying the vector reverse function of the Vector module, we encountered issues in using len(v) inside of the specification expressions.
Referring to len(v) outside of a quantifier range (e.g. first argument to all and any) raises an error.
Also, a local argument whose name is len may conflict with len(v) inside the Boogie models. Refer to https://github.com/libra/libra/pull/4319/commits/3fcb7b44b54924214cb1bb50ad4701515e6fe70f#diff-d85da9b8b2c51c1651760f69f1eff8b4R151.
To reproduce
Removing the comment for line 135 in tests/sources/functional/verify_vector.move (https://github.com/libra/libra/pull/4319/commits/3fcb7b44b54924214cb1bb50ad4701515e6fe70f#diff-d85da9b8b2c51c1651760f69f1eff8b4R135
) and keep the comments for every other line in the spec block to reveal the error below.
Now comment out line 135 and remove the comment for line 138  (https://github.com/libra/libra/pull/4319/commits/3fcb7b44b54924214cb1bb50ad4701515e6fe70f#diff-d85da9b8b2c51c1651760f69f1eff8b4R138), the type checker will no longer raise this error (which is not consistent with the previous error).
Stack trace/error message
error: expected `|vector<#0>|?1` but found `u64` in expression

     ┌── tests/sources/functional/verify_vector.move:123:32 ───
     │
 123 │                 assert (len == len(v));
     │                                ^^^^^^
     │

Expected Behavior
Expected no errors when using a local variable len (issue with variable renaming?) and using len(v) anywhere inside of specification expressions (not just the quantifier range).
System information
Additional context

This is by design. To access a shadowed global name, one can use ::len(x)

authors: kkmc wrwg

repo: libra/libra


text:
errors: finishe converting to use anyhow directly

Finish the work started in #1881 and remove the failure-ext crate

Not sure why bors isn't listening
@bors-libra r=davidiw

:pushpin: Commit 1909c35 has been approved by davidiw

:hourglass: Testing commit 1909c35a674da6bc9808372036e5a7dd10c117e3 with merge b005ed2afbe7c26ad0c8c35b1c2438ed1a80666f...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: davidiw
Pushing b005ed2afbe7c26ad0c8c35b1c2438ed1a80666f to master...

authors: bmwill bors-libra


text:
Update the line format in favour of Markdown syntax

Motivation
I want to contribute to the Blockchain community and get deep into the Libra project.
Have you read the [Contributing Guidelines on pull requests (https://github.com/libra/libra/blob/master/CONTRIBUTING.md#pull-requests)?
Yes
Test Plan
No tests required, only Markdown file updated.
Related PRs
No relation to other PRs

Thanks for the contribution! This looks like a good change.
However, due to some CI changes put in place this last few weeks, to get CI to run we would need you to push against your branch again, or to close this PR and make a new one. Going forward this won't be an issue, but unfortunately, we do not have a nice way to force CI to run for older PRs.

@huitseeker I have added the CI changes.


text:
[dashboard] remove usage of "num_accounts" counter

Motivation
"new_state_leaves" and "stale_state_leaves" in storage were created to provide accurate number of accounts in the system. Gonan delete the old counter (which resets after node restart).
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
play with the dashboard
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/website, and link to your PR here.)

@bors-libra  r=wqfish

:pushpin: Commit 491c9f1 has been approved by wqfish

:hourglass: Testing commit 491c9f1c1bd9e3d2ebd2bf9c41c473a292ceb4d1 with merge caeab05b8016002f67d067b933f730f25044592d...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit 491c9f1c1bd9e3d2ebd2bf9c41c473a292ceb4d1 with merge e89c5229b7484a3c0b89880ff1e0c46af66cd7c7...

:broken_heart: Test failed - checks-actions_land_blocking_test

@bors-libra retry

:hourglass: Testing commit 491c9f1c1bd9e3d2ebd2bf9c41c473a292ceb4d1 with merge a2b96f0bd36210dc5af3fc00a2612a0e9d8160ff...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: wqfish
Pushing a2b96f0bd36210dc5af3fc00a2612a0e9d8160ff to master...

authors: bors-libra msmouse


text:
[mempool] add rebroadcasting txn failures for MempoolIsFull and TooManyTransactions

Motivation
There are some mempool txn submissions that fail that may succeed on retry (e.g. when mempool is full, or an account has too many txns for that mempool locally). This PR adds best-effort rebroadcasting behavior for such txn submission failures.
Test Plan
Existing tests, more tests coming up

@bors-libra r=phoenix-antigravity

:pushpin: Commit a28a947 has been approved by phoenix-antigravity

:hourglass: Testing commit a28a94712044ceb8f5d62a992976900fad3972cb with merge 9f86cf23ab82048cdc3c3b27756183f5839dd0c2...

:broken_heart: Test failed - checks-actions_land_blocking_test

rerunning cluster test myself seems fine... trying again
@bors-libra r=phoenix-antigravity

:bulb: This pull request was already approved, no need to approve it again.

This pull request previously failed. You should add more commits to fix the bug, or use retry to trigger a build again.
There's another pull request that is currently being tested, blocking this pull request: #4248

:pushpin: Commit a28a947 has been approved by phoenix-antigravity

:hourglass: Testing commit a28a94712044ceb8f5d62a992976900fad3972cb with merge 5502844408b8880de7b10da8d8b644ffcd165c18...

authors: bors-libra christinacelee


text:
Bump golang-jwt/jwt from 4.5.0 to 5.2.1

golang-jwt/jwt/v5 saw quite some restructing with regards to the 'Claims' Interface. This commit tries to follow the migration guide from https://github.com/golang-jwt/jwt/blob/bc8bdca5cced1caa9787e4a1c313a3538544c877/MIGRATION_GUIDE.md
Also this removes the no longer used 'signing' package.

I am fine adding checks for the slice being empty, Though as far as I can see the tokens generated by lico are guaranteed to have a value in aud.

I think there is no guarantee about how a token might have been generated when it is presented for validation. Any token can be presented and is validated - so expecting certain things for aud would rely on other previous checks to fail - seems a bad thing to rely on.

signature validation already if the presented token wasn't generated by us, right?

That depends who has one of the valid private keys. That is probably exotic, but technically there is nothing wrong with multiple systems creating lico compatible access tokens. For this it matters little, one of the checks will fail and as long as we don't crash lico when the audience check comes in all should be fine.

So I guess we could just err on the safe side and only consider tokens where len(claims.Audience) is exactly 1.

Ok. I've implemented it this way now. I tried to use the jwt.Validators where possible (Access- and RefreshTokens)

authors: longsleep rhafer

repo: libregraph/lico


text:
uv_udp_send did not send the packet until he receive two packets

Version:   1.39.0
Platform:   linux 18.04

When we sent a packet with uv_udp_send this is not really send until the second packet will came and then two packets together sent to the network.
When you open Wireshark you can see it easily - after two packages arrive they are sent together to the network
This cause latency issues.
In my small program I just receive messages from network on port 18080 and send it to port 18083 and as you can see in the wireshark, insted to recive one message and send it ,the libuv wait until he has two messages and then send them,
the code:
#include <stdio.h>
#include <string.h>
#include
#include
#include "uv.h"
uv_udp_t socket = {};
int SendMsg(const uv_buf_t* buf);
static void PrintLibuvErrorMsg(int err_num) {
char err_message[250] = {0};
uv_strerror_r(err_num, err_message, sizeof(err_message));
printf("Udp Filter: Error - %s\n", err_message);
}
void AllocBufferCb(uv_handle_t* /* handle*/, size_t /suggested_size/,
uv_buf_t* buf) {
unsigned int size = 9000;
char* data = new char[size];
*buf = uv_buf_init(data, size);
}
void OnReceiveCb(uv_udp_t* /req/, ssize_t nread, const uv_buf_t* buf,
const struct sockaddr* addr, unsigned /* flags*/) {
if (buf->base == nullptr) {
printf("Error - No buffer recived\n");
return;  // no buffer, so nothing to do
}
// error
if (nread < 0) {
PrintLibuvErrorMsg((int)nread);
return;
}
// there is no more data to read
if (addr == nullptr) {
return;
}
SendMsg(buf);
}
void OnSendCb(uv_udp_send_t* req, int status) {
char* buf = (char*)req->data;
delete buf;
delete req;  // delete the send request
if (status) {
PrintLibuvErrorMsg(status);
return;
}
}
int SendMsg(const uv_buf_t* buf) {
uv_udp_send_t* send_req{nullptr};
struct sockaddr_in send_addr = {};
uv_buf_t msg = {};
std::string dst_ip{"127.0.0.1"};
uint16_t dst_port{18083};
int res{0};
send_req = new (std::nothrow) uv_udp_send_t;
if (!send_req) {
printf(": Error on memory allocation\n");
goto exit_on_error;
}
memset(send_req, 0, sizeof(uv_udp_send_t));
res = uv_ip4_addr(dst_ip.c_str(), dst_port, &send_addr);
if (res != 0) {
PrintLibuvErrorMsg(res);
goto exit_on_error;
}
send_req->data = buf->base;
msg = uv_buf_init(buf->base, (unsigned int)buf->len);
res = uv_udp_send(send_req, &socket, &msg, 1,
(const struct sockaddr*)&send_addr, OnSendCb);
if (res != 0) {
PrintLibuvErrorMsg(res);
goto exit_on_error;
}
return res;
exit_on_error:
if (send_req != nullptr) {
if (send_req->data != nullptr) {
delete (char*)send_req->data;
}
delete send_req;
}
return res;
}
int main(int /argc/, char** /argv/) {
setvbuf(stdout, NULL, _IONBF, 0);
uv_loop_t* loop = uv_default_loop();
int res = uv_udp_init(loop, &socket);
if (res != 0) {
PrintLibuvErrorMsg(res);
return res;
}
struct sockaddr_in recv_addr;
res = uv_ip4_addr("0.0.0.0", 18080, &recv_addr);
if (res != 0) {
PrintLibuvErrorMsg(res);
return res;
}
res = uv_udp_bind(&socket, (const struct sockaddr*)&recv_addr, 0);
if (res != 0) {
PrintLibuvErrorMsg(res);
return res;
}
res = uv_udp_recv_start(&socket, AllocBufferCb, OnReceiveCb);
if (res != 0) {
PrintLibuvErrorMsg(res);
return res;
}
(void)uv_run(loop, UV_RUN_DEFAULT);
return 0;

The pcap:

The code:
main.txt

You're the author of #3274, right? I'm going to close this as a duplicate, please continue in the other issue.

authors: bnoordhuis ydanzige

repo: libuv/libuv


text:
Revert "Fix cmake build for Windows, with cmake versions before v3.14"

Reverts libuv/libuv#3343
This pull request prevented uv.lib (the import libraries for uv.dll) from being installed.

Thanks for opening this. Would you mind giving #3415 a try to see if it fixes your issue? If so, I think that would be preferable to reverting.

Closing in favor of #3415 which was tested in the conda recipe. Thanks!

authors: SylvainCorlay cjihrig


text:
win: Fix declarations to be C89 compliant for non-relaxed compilers

Visual Studio 2013+ relaxed variable declaration C89 compliance; older
compilers are strict (e.g. VS 2008 - 2012).

LGTM. Maybe you could do the same with dirlen while you're in there.

Are you referring to size_t dirlen = wcslen(dir);? If so it is already compliant; however if you like a nicer cleanup might be the following:
  size_t relpathlen;
  size_t filenamelen = wcslen(filename);
  size_t dirlen = wcslen(dir);
  if (dirlen > 0 && dir[dirlen - 1] == '\\')
    dirlen--;
  relpathlen = filenamelen - dirlen - 1;

LGTM

Rebased and pushed cleanup version

Landed in 3819e48, thanks!

authors: cjihrig mikefero saghul


text:
跨数据库测试

你好，我注意到论文中并未涉及跨数据库的训练测试。本算法是否有进行过跨数据库的数据测试？

@liu0527aa 会议版本没有做跨数据集评估，我们在扩展的期刊版本中做了相关实验，实验结果表明在单个数据集训练其他数据集测试的跨数据集评估设置下，几乎所有的模型都不work。这是由于不同数据集之间的数据分布差异太大以及数据集规模太小模型容易过拟合到当前数据集造成的，所以我们在扩展工作中考虑了混合数据集训练来一定程度缓解过拟合。可以看一下下图的一个结果，文章还在投稿中，所以相关内容暂时未公布。

十分感谢解答，另外由于显存限制，CNN特征提取时，采用不同的 frame_batch_size，是否会影响最终的SRCC？本论文得到的数据采用的 frame_batch_size都是默认64吗？

@liu0527aa 没影响，越小提取特征越慢，显存不够可以设置为1.
我的显存的话提取LIVE-Qualcomm可以用 frame_batch_size=8，可以看特征提取代码中6-8行的注释。


text:
chore: prepare v9.2.1 release

Draft PR to see CI green before tagging and publishing.

Well, I meant to make it a draft PR....

Green:

https://travis-ci.org/liferay/liferay-js-themes-toolkit/builds/553188023
https://travis-ci.org/liferay/liferay-js-themes-toolkit/builds/553188725

repo: liferay/liferay-js-themes-toolkit


text:
Dpp issue 1193

http://www.assembla.com/spaces/liftweb/tickets/1193

Assign to @dpp

Thanks. I've tested this on our app with several layers of ajax-generated functions and it all seems to work :-)
I'm wondering if it's possible to unit test some of this stuff. It seems quite hairy and not always immediately obvious what the issue is or what the semantics are.

authors: dpp jeppenejsum

repo: lift/framework


text:
The har File in Safari doesn't have any data

This is my code:
    int port = 10000;
    server = new BrowserMobProxyServer();
    server.start(port);
    Proxy seleniumProxy = ClientUtil.createSeleniumProxy(server);
    //  pr.setProxyType(Proxy.ProxyType.MANUAL);
    DesiredCapabilities capabilities = new DesiredCapabilities();
    capabilities.setCapability(CapabilityType.PROXY, seleniumProxy);

    driver = new SafariDriver(capabilities);

    server.newHar("myHar");
    driver.get("http://www.google.com");
    Har har = server.getHar();
    Assert.assertTrue(har.getLog().getEntries().size() > 0);

In chrome, the har file contains several entries, as expected. in Safari - it is completely empty.although the webpage opens and everything seemed fine.
Is there some fix or workaround to get the har file to work in safari?
I am using Safari Version 6.2.8 (8537.85.17.9.1) on OSX 10.8.5.
Thanks,
Alina

It sounds like Selenium is having a problem configuring Safari to use a proxy. To test that, try configuring Safari to use the proxy using the standard Safari proxy configuration.

Closing this since there has been no update.

authors: AlinaHeinson jekh

repo: lightbody/browsermob-proxy


text:
Fix error message when no columns found in schema

This PR fixes error message in ParquetMetastoreSupport, so now it shows the original schema and indexed column that does not exist - easier to check original schema. Also wraps column names in messages with quotes.
Closes #71.

Coverage decreased (-0.004%) to 95.845% when pulling 1f7e482e951f39b12a1917226d6cf384f22f4bce on fix-column-not-exist-error-message into c68d07f2f697f630d1d61bc5a6d02a497429d479 on master.

authors: coveralls sadikovi

repo: lightcopy/parquet-index


text:
🛑 Dveri Pax COM is down

In e5eb010, Dveri Pax COM (https://dveri-pax.com) was down:

HTTP code: 500
Response time: 507 ms

Resolved: Dveri Pax COM is back up in ee3f985.

repo: lightcyde/upptime


text:
todo: split like in minicart; possibility to add more links/change entirely

          todo: split like in minicart; possibility to add more links/change entirely

Originally posted by @vileyne in https://github.com/lightna-project/lightna/pull/33#discussion_r1747515231

will be done in the parent ticket

repo: lightna-project/lightna


text:
Memory Leak

I'm researching a memory leak with App. At this point I assume it's in the Renderer based on this:
When I load the TV Grid I have an equal number of ElementNodes (my solid nodes) as Renderer Nodes (Core + Text)

As I navigate a TV grid, creating and removing dozens of nodes per row I end up with roughly the same element nodes as I started with, but the Renderer Nodes are in the thousands. I am calling node.destroy() on the parent node...

PS - I disabled animations and inspector so I don't think those are affecting things. This is with Nodes with children SDF text nodes as well.

I've tested on the solid demo app - went back to version 0.6 and still have a leak with calling destroy() on the lng node.

Way more Renderer nodes than ElementNodes from Solid

I've tracked down a related issue. The emit events are not being cleaned up on all the children nodes. I'm not sure if they are in coreNode. But all textNodes have an on('loaded') listener. When I delete the tree those are still there and not being cleaned up. I see MainCoreNodes is removing listeners but I'm not sure if they also exist on CoreNode?

repo: lightning-js/renderer


text:
No handling for sending on-chain funds to node's pubkey

Background
A user reported to me that they accidentally sent bitcoin to their node's public key as an address, rather than to a deposit address generated by their node (That issue is here: https://github.com/wbobeirne/joule-extension/issues/202). I can imagine this is an easy mistake to make, so it might be nice to account for it. I can think of a few ways to handle this:

Provide an easy way for users to access / rescue funds sent to their node's pubkey.
Don't allow sends to your pubkey (or other node's pubkeys, if this is easy to distinguish) without some kind of flag set.
(Unlikely, but I'll just throw it out there) Differentiate node pubkeys so that they're not valid to send to.

Your environment

version of lnd - 0.6.0-rc3
which operating system (uname -a on *Nix) - Ubuntu 16.04
version of btcd, bitcoind, or other backend - bitcoind

FWIW, sending to a plain pubkey is an accepted Bitcoin transaction type. It's actually the very first Bitcoin transaction type.

Happy to pick this one up, I've made a WIP PR that at the moment checks against the users own Pubkey, ideally it would be better to prevent any Pubkeys?

Yeah I think we should instead prevent any direct pubkey sends as the
wallet doesn't watch for this type of output.
On Tue, Apr 9, 2019, 7:51 PM Christopher Coverdale notifications@github.com
wrote:

Happy to pick this one up, I've made a WIP PR that at the moment checks
against the users own Pubkey, ideally it would be better to prevent any
Pubkeys?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/lightningnetwork/lnd/issues/2920#issuecomment-481513000,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA87LvsAMCsqmCkp1aNGXulIdId9aQLmks5vfVGqgaJpZM4clnuC
.

@Roasbeef awesome, I'll update the PR to prevent any pubkeys as dest

authors: Roasbeef ccdle12 wbobeirne

repo: lightningnetwork/lnd


text:
Negative blocks till maturity on SCB + Seed Restore

EDIT: here are the CNCT logs
https://hastebin.com/vasagicuxa.cs
Background
A while back, my storage device failed and I lost my LND wallet with channels. Fortunately, I had the latest copy of the scb file (channel.backup) and my seed.
When I restore with the seed and copy the scb over, I am able to see my old channels and balances. They were all in “waiting close” for about a week until I tried force closing them, but there was no change.
When I run lncli pendingchannels I see the channels, almost all of which have negative blocks till maturity. Does this means the funds have settled but something isn’t updating to send it back to my lnd wallet?
Your environment

version of lnd
0.9.0 beta
which operating system (uname -a on *Nix)

Linux raspberrypi 4.19.102-v7l+, “Raspiblitz” image

version of btcd, bitcoind, or other backend

Bitcoind 19.0.1

any other relevant environment details
Routed behind the TOR network and successfully connected to 11 peers

Steps to reproduce
Restore using seed + SCB file, use lncli pendingchannels after everything is set up and running
Expected behaviour
Force closed channels should finalize after the blocks till maturity unit is reached
Actual behaviour
Force closed channels are still in a pending state and have a negative value in blocks until maturity
Hastebin output of pending channels:
https://hastebin.com/atilayiwuf.bash

Have you tried multiple restore attempts? If you look at these channels on-chain, all your outputs have already been swept, some of them have even been used for new channels. Could you paste CNCT for 2-3 channels in this state?
Looks similar to https://github.com/lightningnetwork/lnd/issues/3321.

Have you tried multiple restore attempts? If you look at these channels on-chain, all your outputs have already been swept, some of them have even been used for new channels. Could you paste CNCT for 2-3 channels in this state?
Looks similar to #3321.

I have tried multiple restore attempts. I just did one last night and it was probably the 5th or 6th one. The one last night was one week since the previous restore. Every previous restore I have gotten funds swept up but not so with this current attempt.
What’s the best way for me to retrieve the CNCT state of a couple of channels?

Forgot a word:
Could you paste CNCT logs for 2-3 channels in this state?

Here’s
"026165850492521f4ac8abd9bd8088123446d126f648ca35e60f88177dc149ceb2"
https://hastebin.com/igatemuqeq.coffeescript
And now
“026165850492521f4ac8abd9bd8088123446d126f648ca35e60f88177dc149ceb2”
https://hastebin.com/ozacifoqic.coffeescript

We'll need to grep for logs containing [CNCT] for the channel point, not the node public key.

Duplicate of #

We'll need to grep for logs containing [CNCT] for the channel point, not the node public key.

I’m trying when searching the same logs for the channel point instead but it returns nothing. For me the log path is /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log ,
Any suggestions on what command I should use to put the channel point hash into?

We'll need to grep for logs containing [CNCT] for the channel point, not the node public key.

Hi, when I try
sudo cat /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | grep "channelpoint"
I get
2020-02-17 03:37:33.576 [DBG] UTXN: NurseryReport: building nursery report for channel "channel ID"
Any idea where I can go to access the NurseyReports?

After doing more research, it seems like I need to turn on CNCT trace.
But when I do
lncli debuglevel CNCT=trace
I get
[lncli] rpc error: code = Unknown desc = the specified debug level [] is invalid
Any ideas what is wrong with my syntax?

sudo cat /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | grep "channelpoint"

Try grep -i to do case insensitive search, most likely ChannelPoint is written camel case in most cases (but perhaps not always).
You can use the --help flag for all lncli commands. That will tell you that the command is lncli debuglevel --level CNCT=trace

sudo cat /mnt/hdd/lnd/logs/bitcoin/mainnet/lnd.log | grep "channelpoint"

Try grep -i to do case insensitive search, most likely ChannelPoint is written camel case in most cases (but perhaps not always).
You can use the --help flag for all lncli commands. That will tell you that the command is lncli debuglevel --level CNCT=trace

Thank you! I’ll try this. I was trying to use the help command but didn’t quite understand how the level syntax was supposed to work. Thank you though.
I should also clarify, the channel point reference I had in my previous post is the placeholder for the value next to channel point when using the lncli pendingchannels command

We'll need to grep for logs containing [CNCT] for the channel point, not the node public key.

Here are the CNCT logs
https://hastebin.com/vasagicuxa.cs

And here are some more
https://hastebin.com/okibezuzoz.sql

Thanks for the logs! I went through each channel and confirmed that all the funds been swept, so you should have the balance in your on-chain wallet. The fact that the channels remain in pendingchannels is a bug within lnd where it doesn't recognize previous channel restore attempts. Closing this as a duplicate of #3321.

Thanks for the logs! I went through each channel and confirmed that all the funds been swept, so you should have the balance in your on-chain wallet. The fact that the channels remain in pendingchannels is a bug within lnd where it doesn't recognize previous channel restore attempts. Closing this as a duplicate of #3321.

If I don’t have the balance with my on chain wallet, is there something I can do to prompt the node to scan and pick it up?

If you already recovered from your seed, the balance should be there unless you already spent those funds elsewhere. For example, if you look at the channel 19efead5d19f0a51bfe0763715bee528e36fd5f5cbf40723b34fd5977d4efa00, the closing transaction is cdae9571f97fb2c5758f6d2e2f59d1465a1fa6d2a2e4a73ff1964c67fcf13e62, and the transaction that returned the funds back to your wallet is 5841b42f4280d7f83120a5e55890af6906537864423a7716751fecdb63562773. From there, you can track where the funds may have gone.

authors: guggero thelightningist wpaulino


text:
Lnd with Neutrino is not broadcasting on-chain transaction to the bitcoin network

Background
Hi, I'm not sure if this issue should be opened in the neutrino project or here.
I am having some trouble sending on-chain transactions, seemingly they're never published/relayed.
This is with lnd 0.20.1 using Neutrino and connecting to a bitcoind 0.21.0 node serving compact filters.
Both SendCoins and OpenChannel seems to be affected by this.
On the bitcoind side I tried putting mempool debug logging on, but no transaction is ever received.
On the lnd side I see nothing unusual:
2021-03-20 19:13:08.043 [INF] RPCS: [sendcoins] addr=tb1qyvugphjf6wfuzuqvwf2sl20gtxpa46k9af0zcx, amt=0.0005 BTC, sat/kw=12500, min_confs=1, send_all=false
2021-03-20 19:13:08.086 [INF] LNWL: Inserting unconfirmed transaction 516e19659f516dc830ab45da3c8e31fe2c056509a56039906d2ef115c907733d
2021-03-20 19:13:08.632 [INF] RPCS: [sendcoins] spend generated txid: 516e19659f516dc830ab45da3c8e31fe2c056509a56039906d2ef115c907733d

The configuration is nothing unusual AFAICT, on the bitcoind side (omitted comments etc to keep it small):
txindex=1

zmqpubrawblock=tcp://127.0.0.1:28334
zmqpubrawtx=tcp://127.0.0.1:29335

blockfilterindex=1
peerblockfilters=1

loglevel=debug
category=mempool
debug=mempool

testnet=1

listen=1

rpcuser=[redacted]
rpcpassword=[redacted]

rpcport=8332

[test]
port=18333
rpcport=18332
rpcbind=[redacted]

On the lnd side, see here.
Your environment

lnd 0.20.1 with Neutrino
bitcoind 0.21.0 as the Compact Filter server
Mostly tested on my mobile wallet (Gomobile Android/iOS), but I confirmed it's happening on normal desktop MacOS as well, which is why I am choosing to open the issue

Steps to reproduce

Set up a bitcoind 0.21.0 node serving compact filters.
Hook up lnd+neutrino with neutrino.connect=<bitcoind node>
Send coins to lnd's internal wallet
Spend these coins
The transaction generated from lnd/btcwallet is seemingly never published (doesn't appear on block explorers etc). This applies to both mainnet and testnet. On mainnet I double-checked bitcoin-cli testmempoolaccept ... on the bitcoind peer to make sure the transaction valid and has enough fees.

Expected behaviour
On-chain transactions created by lnd/btcwallet should relayed to the Neutrino peer.
Actual behaviour
Lnd/btcwallet seemingly never relays on-chain transactions to the Neutrino peer.

Is the transaction actually valid?  I keep having issues where my node tries to spend coins that have already been spent (into a Pool account) and it keeps an invalid pending utxo in the wallet that you have to rescan the chain to clear out.

Did you try the exact same setup just using btcd instead? Would be interesting to see if in that case it gets published.

Also if you re-run it with full debug/trace logs for BTCN on the neutrino node, do you see it actually publish the transaction? Neutrino will also re-publish in the background until either it's restarted (then it'll continue to do so if still unconfirmed), or it gets confirmed.

@delbonis I think the transaction is valid. I tested it with bitcoin-cli testmempoolaccept, which I assume will check if the script is actually valid.
@halseth Yes, my initial thought was some kind of incompatibility with bitcoind. I'll try what happens with btcd.
@Roasbeef Thanks, I'll try that and report back.

@halseth Using btcd 0.21.0-beta instead of bitcoind 0.21.0 works fine. Same setup.

Was the transaction perhaps one of a relatively low fee? btcd doesn't implement a dynamic mempool fee requirement quite in the same way that bitcoind does.

@Roasbeef I don't believe that's the case. This is happening on both mainnet and testnet. On mainnet I made sure to have sufficient tx fee (by checking on https://mempool.space), I also double-checked the tx hex with bitcoin-cli testmempoolaccept ... on the bitcoind neutrino peer to make sure it would accept the transaction.
Note that this isn't a one time incident, I can easily reproduce it on testnet and I believe @torkelrogstad has encountered into the same problem at least once.

@wpaulino Initial testing suggests that yes, increasing the timeout solves the problem!
I have opened a pull request over at the Neutrino repository addressing this. 500ms seems unnecessarily short.

@hsjoberg In my case the transaction actually is invalid, trying to manually give it to a node it rejects it because the input was already spent.

Fix was merged over at the Neutrino repo https://github.com/lightninglabs/neutrino/commit/62e95cdcbf33d67a2c420f5015040dd3761e567a.
I'm opening a pull request to update the Neutrino version to use in lnd: #5170

authors: Roasbeef delbonis halseth hsjoberg