BTCPay teos Tor

Hi,
It seems that teos integration in BTCPay-dockerized latest stable version is not working either via ipv4:port tor:port nothing works. Any idea where to start and or what to track?

I'm giving a look at it at the moment.
Any additional info would help.

Here it is, some error keeps repeating from time to time, and the startup its weird also:
root@btc:~/btcpayserver-docker# docker logs generated_bitcoin_teos_1
27/02/2021 16:01:33 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:33 [Daemon] ERROR: An error occurred: Cannot connect to bitcoind. Shutting down
27/02/2021 16:01:37 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:41 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:41 [Daemon] ERROR: An error occurred: Cannot connect to bitcoind. Shutting down
27/02/2021 16:01:48 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:48 [Daemon] tower_id = 026247def18440eb3a3e59be829b7c12dd2e86da6989b88644de306132adf72761
27/02/2021 16:01:49 [Daemon] Starting TEOS
27/02/2021 16:01:49 [Daemon] Fresh bootstrap
27/02/2021 16:01:49 [Daemon] Internal API initialized. Serving at localhost:50051
[2021-02-27 16:01:49 +0000] [30] [INFO] Starting gunicorn 20.0.4
[2021-02-27 16:01:49 +0000] [30] [INFO] Listening at: http://<IP_ADDRESS>:9814 (30)
[2021-02-27 16:01:49 +0000] [30] [INFO] Using worker: sync
[2021-02-27 16:01:49 +0000] [31] [INFO] Booting worker with pid: 31
27/02/2021 16:01:49 [RPC] Initialized. Serving at localhost:8814
27/02/2021 16:01:49 [API] Initialized. Serving at <IP_ADDRESS>:9814
27/02/2021 16:20:40 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000000564444c8b005b5bb6942e6023844842b81a10bc8bf4b)
27/02/2021 16:20:41 [Watcher] New block received  (block_hash=00000000000000000000564444c8b005b5bb6942e6023844842b81a10bc8bf4b, prev_block_hash=00000000000000000008e2b41bf3415514e4e1a5d741971f38e75443d88046ee)
27/02/2021 16:20:41 [Responder] New block received  (block_hash=00000000000000000000564444c8b005b5bb6942e6023844842b81a10bc8bf4b, prev_block_hash=00000000000000000008e2b41bf3415514e4e1a5d741971f38e75443d88046ee)
27/02/2021 16:35:17 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000049f53a64e4f30e5c7ae180ee6ff5f91a65c01340dc79e)
27/02/2021 16:35:17 [Responder] New block received  (block_hash=000000000000000000049f53a64e4f30e5c7ae180ee6ff5f91a65c01340dc79e, prev_block_hash=00000000000000000000564444c8b005b5bb6942e6023844842b81a10bc8bf4b)
27/02/2021 16:35:17 [Watcher] New block received  (block_hash=000000000000000000049f53a64e4f30e5c7ae180ee6ff5f91a65c01340dc79e, prev_block_hash=00000000000000000000564444c8b005b5bb6942e6023844842b81a10bc8bf4b)
27/02/2021 16:45:23 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000000450cba6f5a4fabb3cf5294c63592c145adc2238722cf)
27/02/2021 16:45:23 [Watcher] New block received  (block_hash=00000000000000000000450cba6f5a4fabb3cf5294c63592c145adc2238722cf, prev_block_hash=000000000000000000049f53a64e4f30e5c7ae180ee6ff5f91a65c01340dc79e)
27/02/2021 16:45:23 [Responder] New block received  (block_hash=00000000000000000000450cba6f5a4fabb3cf5294c63592c145adc2238722cf, prev_block_hash=000000000000000000049f53a64e4f30e5c7ae180ee6ff5f91a65c01340dc79e)
27/02/2021 16:50:40 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000a853826cbab7fd1d283b074449f863b98700bc8580625)
27/02/2021 16:50:40 [Responder] New block received  (block_hash=0000000000000000000a853826cbab7fd1d283b074449f863b98700bc8580625, prev_block_hash=00000000000000000000450cba6f5a4fabb3cf5294c63592c145adc2238722cf)
27/02/2021 16:50:40 [Watcher] New block received  (block_hash=0000000000000000000a853826cbab7fd1d283b074449f863b98700bc8580625, prev_block_hash=00000000000000000000450cba6f5a4fabb3cf5294c63592c145adc2238722cf)
27/02/2021 17:03:29 [Daemon] Tower identity found. Loading keys
27/02/2021 17:03:29 [Daemon] tower_id = 026247def18440eb3a3e59be829b7c12dd2e86da6989b88644de306132adf72761
27/02/2021 17:03:29 [Daemon] Starting TEOS
27/02/2021 17:03:29 [Daemon] Fresh bootstrap
27/02/2021 17:03:29 [Daemon] Internal API initialized. Serving at localhost:50051
27/02/2021 17:03:30 [RPC] Initialized. Serving at localhost:8814
[2021-02-27 17:03:30 +0000] [30] [INFO] Starting gunicorn 20.0.4
[2021-02-27 17:03:30 +0000] [30] [INFO] Listening at: http://<IP_ADDRESS>:9814 (30)
[2021-02-27 17:03:30 +0000] [30] [INFO] Using worker: sync
[2021-02-27 17:03:30 +0000] [36] [INFO] Booting worker with pid: 36
27/02/2021 17:03:30 [API] Initialized. Serving at <IP_ADDRESS>:9814
27/02/2021 17:14:34 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000031dd30757501a8cd7374bec9a6edb2824c17aff5b4340)
27/02/2021 17:14:34 [Watcher] New block received  (block_hash=000000000000000000031dd30757501a8cd7374bec9a6edb2824c17aff5b4340, prev_block_hash=0000000000000000000a853826cbab7fd1d283b074449f863b98700bc8580625)
27/02/2021 17:14:34 [Responder] New block received  (block_hash=000000000000000000031dd30757501a8cd7374bec9a6edb2824c17aff5b4340, prev_block_hash=0000000000000000000a853826cbab7fd1d283b074449f863b98700bc8580625)
27/02/2021 17:14:54 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000009b4a455271f63b53624b6f590a86ac6565e80e1c7e9be)
27/02/2021 17:14:54 [Responder] New block received  (block_hash=00000000000000000009b4a455271f63b53624b6f590a86ac6565e80e1c7e9be, prev_block_hash=000000000000000000031dd30757501a8cd7374bec9a6edb2824c17aff5b4340)
27/02/2021 17:14:54 [Watcher] New block received  (block_hash=00000000000000000009b4a455271f63b53624b6f590a86ac6565e80e1c7e9be, prev_block_hash=000000000000000000031dd30757501a8cd7374bec9a6edb2824c17aff5b4340)
27/02/2021 17:24:15 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000008f4f145b65396f92cea6bb500b0d922ec94c1730dad83)
27/02/2021 17:24:15 [Responder] New block received  (block_hash=00000000000000000008f4f145b65396f92cea6bb500b0d922ec94c1730dad83, prev_block_hash=00000000000000000009b4a455271f63b53624b6f590a86ac6565e80e1c7e9be)
27/02/2021 17:24:15 [Watcher] New block received  (block_hash=00000000000000000008f4f145b65396f92cea6bb500b0d922ec94c1730dad83, prev_block_hash=00000000000000000009b4a455271f63b53624b6f590a86ac6565e80e1c7e9be)
27/02/2021 17:26:44 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000008a3c9f745769d9a58ba321dc32c0a5ca54ae652c9f6aa)
27/02/2021 17:26:44 [Responder] New block received  (block_hash=00000000000000000008a3c9f745769d9a58ba321dc32c0a5ca54ae652c9f6aa, prev_block_hash=00000000000000000008f4f145b65396f92cea6bb500b0d922ec94c1730dad83)
27/02/2021 17:26:44 [Watcher] New block received  (block_hash=00000000000000000008a3c9f745769d9a58ba321dc32c0a5ca54ae652c9f6aa, prev_block_hash=00000000000000000008f4f145b65396f92cea6bb500b0d922ec94c1730dad83)
27/02/2021 17:29:29 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000005ee92a6f587ff582dccdf717c7f5a8db1086c0da3d5fa)
27/02/2021 17:29:29 [Watcher] New block received  (block_hash=00000000000000000005ee92a6f587ff582dccdf717c7f5a8db1086c0da3d5fa, prev_block_hash=00000000000000000008a3c9f745769d9a58ba321dc32c0a5ca54ae652c9f6aa)
27/02/2021 17:29:29 [Responder] New block received  (block_hash=00000000000000000005ee92a6f587ff582dccdf717c7f5a8db1086c0da3d5fa, prev_block_hash=00000000000000000008a3c9f745769d9a58ba321dc32c0a5ca54ae652c9f6aa)
27/02/2021 17:36:29 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000001cf0b8d58903d6bba81c93a1def6596f6ca78d81447c1)
27/02/2021 17:36:29 [Watcher] New block received  (block_hash=00000000000000000001cf0b8d58903d6bba81c93a1def6596f6ca78d81447c1, prev_block_hash=00000000000000000005ee92a6f587ff582dccdf717c7f5a8db1086c0da3d5fa)
27/02/2021 17:36:29 [Responder] New block received  (block_hash=00000000000000000001cf0b8d58903d6bba81c93a1def6596f6ca78d81447c1, prev_block_hash=00000000000000000005ee92a6f587ff582dccdf717c7f5a8db1086c0da3d5fa)
27/02/2021 17:51:25 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000072237d3be5dd3f46837ee86542802a0ebb21e6c6968f6)
27/02/2021 17:51:25 [Watcher] New block received  (block_hash=000000000000000000072237d3be5dd3f46837ee86542802a0ebb21e6c6968f6, prev_block_hash=00000000000000000001cf0b8d58903d6bba81c93a1def6596f6ca78d81447c1)
27/02/2021 17:51:25 [Responder] New block received  (block_hash=000000000000000000072237d3be5dd3f46837ee86542802a0ebb21e6c6968f6, prev_block_hash=00000000000000000001cf0b8d58903d6bba81c93a1def6596f6ca78d81447c1)
27/02/2021 17:52:55 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000a8b4b4ebd9e3ec670fc99e3b86c7951590745d8fc645b)
27/02/2021 17:52:55 [Responder] New block received  (block_hash=0000000000000000000a8b4b4ebd9e3ec670fc99e3b86c7951590745d8fc645b, prev_block_hash=000000000000000000072237d3be5dd3f46837ee86542802a0ebb21e6c6968f6)
27/02/2021 17:52:55 [Watcher] New block received  (block_hash=0000000000000000000a8b4b4ebd9e3ec670fc99e3b86c7951590745d8fc645b, prev_block_hash=000000000000000000072237d3be5dd3f46837ee86542802a0ebb21e6c6968f6)
27/02/2021 18:01:26 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000003563a63eaa804414c182eef2127fe4aae9e61f5a2138d)
27/02/2021 18:01:26 [Watcher] New block received  (block_hash=00000000000000000003563a63eaa804414c182eef2127fe4aae9e61f5a2138d, prev_block_hash=0000000000000000000a8b4b4ebd9e3ec670fc99e3b86c7951590745d8fc645b)
27/02/2021 18:01:26 [Responder] New block received  (block_hash=00000000000000000003563a63eaa804414c182eef2127fe4aae9e61f5a2138d, prev_block_hash=0000000000000000000a8b4b4ebd9e3ec670fc99e3b86c7951590745d8fc645b)
27/02/2021 18:08:16 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000090ef0d38c6a5a8b7bf9348dbcb3dc801a0289fcd9bd29)
27/02/2021 18:08:16 [Responder] New block received  (block_hash=000000000000000000090ef0d38c6a5a8b7bf9348dbcb3dc801a0289fcd9bd29, prev_block_hash=00000000000000000003563a63eaa804414c182eef2127fe4aae9e61f5a2138d)
27/02/2021 18:08:16 [Watcher] New block received  (block_hash=000000000000000000090ef0d38c6a5a8b7bf9348dbcb3dc801a0289fcd9bd29, prev_block_hash=00000000000000000003563a63eaa804414c182eef2127fe4aae9e61f5a2138d)
27/02/2021 18:22:01 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000004c423a33586a0d8dbbd2d4f1122d16cfe11742181b688)
27/02/2021 18:22:01 [Responder] New block received  (block_hash=00000000000000000004c423a33586a0d8dbbd2d4f1122d16cfe11742181b688, prev_block_hash=000000000000000000090ef0d38c6a5a8b7bf9348dbcb3dc801a0289fcd9bd29)
27/02/2021 18:22:01 [Watcher] New block received  (block_hash=00000000000000000004c423a33586a0d8dbbd2d4f1122d16cfe11742181b688, prev_block_hash=000000000000000000090ef0d38c6a5a8b7bf9348dbcb3dc801a0289fcd9bd29)
27/02/2021 18:54:30 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000081562e321c0528643d92508555707f02e702b3846578)
27/02/2021 18:54:30 [Responder] New block received  (block_hash=0000000000000000000081562e321c0528643d92508555707f02e702b3846578, prev_block_hash=00000000000000000004c423a33586a0d8dbbd2d4f1122d16cfe11742181b688)
27/02/2021 18:54:30 [Watcher] New block received  (block_hash=0000000000000000000081562e321c0528643d92508555707f02e702b3846578, prev_block_hash=00000000000000000004c423a33586a0d8dbbd2d4f1122d16cfe11742181b688)
27/02/2021 18:55:14 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000006644ad08cd575c280aab60e2a8e67cf7bba703565d5aa)
27/02/2021 18:55:14 [Watcher] New block received  (block_hash=00000000000000000006644ad08cd575c280aab60e2a8e67cf7bba703565d5aa, prev_block_hash=0000000000000000000081562e321c0528643d92508555707f02e702b3846578)
27/02/2021 18:55:14 [Responder] New block received  (block_hash=00000000000000000006644ad08cd575c280aab60e2a8e67cf7bba703565d5aa, prev_block_hash=0000000000000000000081562e321c0528643d92508555707f02e702b3846578)
27/02/2021 18:56:24 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000b691cd63d88edb465e43b477948d9fd82d1e927b15eb6)
27/02/2021 18:56:24 [Responder] New block received  (block_hash=0000000000000000000b691cd63d88edb465e43b477948d9fd82d1e927b15eb6, prev_block_hash=00000000000000000006644ad08cd575c280aab60e2a8e67cf7bba703565d5aa)
27/02/2021 18:56:24 [Watcher] New block received  (block_hash=0000000000000000000b691cd63d88edb465e43b477948d9fd82d1e927b15eb6, prev_block_hash=00000000000000000006644ad08cd575c280aab60e2a8e67cf7bba703565d5aa)
27/02/2021 19:04:59 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000001cadb8fe9824fd0778a551445ca3c82a8edd52ee78a2b)
27/02/2021 19:05:00 [Watcher] New block received  (block_hash=00000000000000000001cadb8fe9824fd0778a551445ca3c82a8edd52ee78a2b, prev_block_hash=0000000000000000000b691cd63d88edb465e43b477948d9fd82d1e927b15eb6)
27/02/2021 19:05:00 [Responder] New block received  (block_hash=00000000000000000001cadb8fe9824fd0778a551445ca3c82a8edd52ee78a2b, prev_block_hash=0000000000000000000b691cd63d88edb465e43b477948d9fd82d1e927b15eb6)
27/02/2021 19:22:32 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000074b9d187cca8c5b69dc636f3640d04423705a10715d70)
27/02/2021 19:22:32 [Watcher] New block received  (block_hash=000000000000000000074b9d187cca8c5b69dc636f3640d04423705a10715d70, prev_block_hash=00000000000000000001cadb8fe9824fd0778a551445ca3c82a8edd52ee78a2b)
27/02/2021 19:22:32 [Responder] New block received  (block_hash=000000000000000000074b9d187cca8c5b69dc636f3640d04423705a10715d70, prev_block_hash=00000000000000000001cadb8fe9824fd0778a551445ca3c82a8edd52ee78a2b)
27/02/2021 19:34:47 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000007d34ecc4de69e3f6659535669733ea349f1872095a3eb)
27/02/2021 19:34:47 [Watcher] New block received  (block_hash=00000000000000000007d34ecc4de69e3f6659535669733ea349f1872095a3eb, prev_block_hash=000000000000000000074b9d187cca8c5b69dc636f3640d04423705a10715d70)
27/02/2021 19:34:47 [Responder] New block received  (block_hash=00000000000000000007d34ecc4de69e3f6659535669733ea349f1872095a3eb, prev_block_hash=000000000000000000074b9d187cca8c5b69dc636f3640d04423705a10715d70)
27/02/2021 19:36:01 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c0f2eb49170779b9277cdfaaead94395711ef242ee255)
27/02/2021 19:36:01 [Responder] New block received  (block_hash=0000000000000000000c0f2eb49170779b9277cdfaaead94395711ef242ee255, prev_block_hash=00000000000000000007d34ecc4de69e3f6659535669733ea349f1872095a3eb)
27/02/2021 19:36:01 [Watcher] New block received  (block_hash=0000000000000000000c0f2eb49170779b9277cdfaaead94395711ef242ee255, prev_block_hash=00000000000000000007d34ecc4de69e3f6659535669733ea349f1872095a3eb)
27/02/2021 19:37:38 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000008c3e0d4288ef0d8b2474abd322fd35b5bed69a5cd4158)
27/02/2021 19:37:38 [Watcher] New block received  (block_hash=00000000000000000008c3e0d4288ef0d8b2474abd322fd35b5bed69a5cd4158, prev_block_hash=0000000000000000000c0f2eb49170779b9277cdfaaead94395711ef242ee255)
27/02/2021 19:37:38 [Responder] New block received  (block_hash=00000000000000000008c3e0d4288ef0d8b2474abd322fd35b5bed69a5cd4158, prev_block_hash=0000000000000000000c0f2eb49170779b9277cdfaaead94395711ef242ee255)
27/02/2021 19:43:18 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000182d8acc52e4cdc4a1b3480850e9904575f3ff8fc5873)
27/02/2021 19:43:18 [Responder] New block received  (block_hash=0000000000000000000182d8acc52e4cdc4a1b3480850e9904575f3ff8fc5873, prev_block_hash=00000000000000000008c3e0d4288ef0d8b2474abd322fd35b5bed69a5cd4158)
27/02/2021 19:43:18 [Watcher] New block received  (block_hash=0000000000000000000182d8acc52e4cdc4a1b3480850e9904575f3ff8fc5873, prev_block_hash=00000000000000000008c3e0d4288ef0d8b2474abd322fd35b5bed69a5cd4158)
27/02/2021 19:45:05 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000957793c7f9bc44044ddaac907591e2ef1ee36d5e8c448)
27/02/2021 19:45:05 [Responder] New block received  (block_hash=0000000000000000000957793c7f9bc44044ddaac907591e2ef1ee36d5e8c448, prev_block_hash=0000000000000000000182d8acc52e4cdc4a1b3480850e9904575f3ff8fc5873)
27/02/2021 19:45:05 [Watcher] New block received  (block_hash=0000000000000000000957793c7f9bc44044ddaac907591e2ef1ee36d5e8c448, prev_block_hash=0000000000000000000182d8acc52e4cdc4a1b3480850e9904575f3ff8fc5873)
27/02/2021 19:51:37 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000003034338d5e29648e175ad3c85723045ff0524de7a7542)
27/02/2021 19:51:37 [Responder] New block received  (block_hash=00000000000000000003034338d5e29648e175ad3c85723045ff0524de7a7542, prev_block_hash=0000000000000000000957793c7f9bc44044ddaac907591e2ef1ee36d5e8c448)
27/02/2021 19:51:37 [Watcher] New block received  (block_hash=00000000000000000003034338d5e29648e175ad3c85723045ff0524de7a7542, prev_block_hash=0000000000000000000957793c7f9bc44044ddaac907591e2ef1ee36d5e8c448)
27/02/2021 20:01:51 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000000368cd2eaab5ab9598b51f01ebce83ea8419232a66e9d)
27/02/2021 20:01:51 [Watcher] New block received  (block_hash=00000000000000000000368cd2eaab5ab9598b51f01ebce83ea8419232a66e9d, prev_block_hash=00000000000000000003034338d5e29648e175ad3c85723045ff0524de7a7542)
27/02/2021 20:01:51 [Responder] New block received  (block_hash=00000000000000000000368cd2eaab5ab9598b51f01ebce83ea8419232a66e9d, prev_block_hash=00000000000000000003034338d5e29648e175ad3c85723045ff0524de7a7542)
27/02/2021 20:03:56 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000b6549205de4024e92b9bdc21f87017adf1a01dc81a896)
27/02/2021 20:03:56 [Watcher] New block received  (block_hash=0000000000000000000b6549205de4024e92b9bdc21f87017adf1a01dc81a896, prev_block_hash=00000000000000000000368cd2eaab5ab9598b51f01ebce83ea8419232a66e9d)
27/02/2021 20:03:56 [Responder] New block received  (block_hash=0000000000000000000b6549205de4024e92b9bdc21f87017adf1a01dc81a896, prev_block_hash=00000000000000000000368cd2eaab5ab9598b51f01ebce83ea8419232a66e9d)
27/02/2021 20:26:05 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000cae534e4d44a2278f575e56a5f967ef18ba916a16806d)
27/02/2021 20:26:06 [Watcher] New block received  (block_hash=0000000000000000000cae534e4d44a2278f575e56a5f967ef18ba916a16806d, prev_block_hash=0000000000000000000b6549205de4024e92b9bdc21f87017adf1a01dc81a896)
27/02/2021 20:26:06 [Responder] New block received  (block_hash=0000000000000000000cae534e4d44a2278f575e56a5f967ef18ba916a16806d, prev_block_hash=0000000000000000000b6549205de4024e92b9bdc21f87017adf1a01dc81a896)
27/02/2021 20:37:22 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000006a2a8f976a5ba4decd4bf724290b9db64fce935c7960d)
27/02/2021 20:37:22 [Watcher] New block received  (block_hash=00000000000000000006a2a8f976a5ba4decd4bf724290b9db64fce935c7960d, prev_block_hash=0000000000000000000cae534e4d44a2278f575e56a5f967ef18ba916a16806d)
27/02/2021 20:37:22 [Responder] New block received  (block_hash=00000000000000000006a2a8f976a5ba4decd4bf724290b9db64fce935c7960d, prev_block_hash=0000000000000000000cae534e4d44a2278f575e56a5f967ef18ba916a16806d)
27/02/2021 21:06:33 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000007d701ed789c6831cec5bdc8ae859b13ecb71eb185a29e)
27/02/2021 21:06:33 [Watcher] New block received  (block_hash=00000000000000000007d701ed789c6831cec5bdc8ae859b13ecb71eb185a29e, prev_block_hash=00000000000000000006a2a8f976a5ba4decd4bf724290b9db64fce935c7960d)
27/02/2021 21:06:33 [Responder] New block received  (block_hash=00000000000000000007d701ed789c6831cec5bdc8ae859b13ecb71eb185a29e, prev_block_hash=00000000000000000006a2a8f976a5ba4decd4bf724290b9db64fce935c7960d)
27/02/2021 21:29:21 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000532fccdb8329d0ae1ba59c9f43471e6e4a1efe69e9100)
27/02/2021 21:29:21 [Watcher] New block received  (block_hash=0000000000000000000532fccdb8329d0ae1ba59c9f43471e6e4a1efe69e9100, prev_block_hash=00000000000000000007d701ed789c6831cec5bdc8ae859b13ecb71eb185a29e)
27/02/2021 21:29:21 [Responder] New block received  (block_hash=0000000000000000000532fccdb8329d0ae1ba59c9f43471e6e4a1efe69e9100, prev_block_hash=00000000000000000007d701ed789c6831cec5bdc8ae859b13ecb71eb185a29e)
27/02/2021 21:42:05 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000009a5fbe17ed811f49ef03ae883cc88f6baeb51852ab3ac)
27/02/2021 21:42:05 [Watcher] New block received  (block_hash=00000000000000000009a5fbe17ed811f49ef03ae883cc88f6baeb51852ab3ac, prev_block_hash=0000000000000000000532fccdb8329d0ae1ba59c9f43471e6e4a1efe69e9100)
27/02/2021 21:42:05 [Responder] New block received  (block_hash=00000000000000000009a5fbe17ed811f49ef03ae883cc88f6baeb51852ab3ac, prev_block_hash=0000000000000000000532fccdb8329d0ae1ba59c9f43471e6e4a1efe69e9100)
27/02/2021 22:01:05 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000006cae670f70127ec3d6422aad0d61d9984178c0caa2e02)
27/02/2021 22:01:05 [Watcher] New block received  (block_hash=00000000000000000006cae670f70127ec3d6422aad0d61d9984178c0caa2e02, prev_block_hash=00000000000000000009a5fbe17ed811f49ef03ae883cc88f6baeb51852ab3ac)
27/02/2021 22:01:05 [Responder] New block received  (block_hash=00000000000000000006cae670f70127ec3d6422aad0d61d9984178c0caa2e02, prev_block_hash=00000000000000000009a5fbe17ed811f49ef03ae883cc88f6baeb51852ab3ac)
27/02/2021 22:20:13 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000201084b7f4b42f95c1e01923dda308f944ee9ce936661)
27/02/2021 22:20:13 [Watcher] New block received  (block_hash=0000000000000000000201084b7f4b42f95c1e01923dda308f944ee9ce936661, prev_block_hash=00000000000000000006cae670f70127ec3d6422aad0d61d9984178c0caa2e02)
27/02/2021 22:20:13 [Responder] New block received  (block_hash=0000000000000000000201084b7f4b42f95c1e01923dda308f944ee9ce936661, prev_block_hash=00000000000000000006cae670f70127ec3d6422aad0d61d9984178c0caa2e02)
27/02/2021 22:35:00 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c6ccf9473f54126cf1c1bbc2086e123dc26d816276a35)
27/02/2021 22:35:00 [Watcher] New block received  (block_hash=0000000000000000000c6ccf9473f54126cf1c1bbc2086e123dc26d816276a35, prev_block_hash=0000000000000000000201084b7f4b42f95c1e01923dda308f944ee9ce936661)
27/02/2021 22:35:00 [Responder] New block received  (block_hash=0000000000000000000c6ccf9473f54126cf1c1bbc2086e123dc26d816276a35, prev_block_hash=0000000000000000000201084b7f4b42f95c1e01923dda308f944ee9ce936661)
27/02/2021 22:57:31 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c315e04e62f4a940ae70757c22b6bdaf6680efb5da013)
27/02/2021 22:57:31 [Watcher] New block received  (block_hash=0000000000000000000c315e04e62f4a940ae70757c22b6bdaf6680efb5da013, prev_block_hash=0000000000000000000c6ccf9473f54126cf1c1bbc2086e123dc26d816276a35)
27/02/2021 22:57:31 [Responder] New block received  (block_hash=0000000000000000000c315e04e62f4a940ae70757c22b6bdaf6680efb5da013, prev_block_hash=0000000000000000000c6ccf9473f54126cf1c1bbc2086e123dc26d816276a35)
27/02/2021 23:03:06 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000009d4c70612485bd3a8f4fb05cc04bb12a47084884c0381)
27/02/2021 23:03:06 [Watcher] New block received  (block_hash=00000000000000000009d4c70612485bd3a8f4fb05cc04bb12a47084884c0381, prev_block_hash=0000000000000000000c315e04e62f4a940ae70757c22b6bdaf6680efb5da013)
27/02/2021 23:03:06 [Responder] New block received  (block_hash=00000000000000000009d4c70612485bd3a8f4fb05cc04bb12a47084884c0381, prev_block_hash=0000000000000000000c315e04e62f4a940ae70757c22b6bdaf6680efb5da013)
27/02/2021 23:08:02 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000002d56ca740d0346c0c9522bd2636d5e260a975280c2588)
27/02/2021 23:08:02 [Watcher] New block received  (block_hash=00000000000000000002d56ca740d0346c0c9522bd2636d5e260a975280c2588, prev_block_hash=00000000000000000009d4c70612485bd3a8f4fb05cc04bb12a47084884c0381)
27/02/2021 23:08:02 [Responder] New block received  (block_hash=00000000000000000002d56ca740d0346c0c9522bd2636d5e260a975280c2588, prev_block_hash=00000000000000000009d4c70612485bd3a8f4fb05cc04bb12a47084884c0381)
27/02/2021 23:11:10 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000077b8a2453eb2544db153dcf9d17923b17e6d194a50934)
27/02/2021 23:11:10 [Watcher] New block received  (block_hash=000000000000000000077b8a2453eb2544db153dcf9d17923b17e6d194a50934, prev_block_hash=00000000000000000002d56ca740d0346c0c9522bd2636d5e260a975280c2588)
27/02/2021 23:11:10 [Responder] New block received  (block_hash=000000000000000000077b8a2453eb2544db153dcf9d17923b17e6d194a50934, prev_block_hash=00000000000000000002d56ca740d0346c0c9522bd2636d5e260a975280c2588)
27/02/2021 23:25:14 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000745d736aa6e6d548d17006aaa84a9204801e05735377f)
27/02/2021 23:25:14 [Responder] New block received  (block_hash=0000000000000000000745d736aa6e6d548d17006aaa84a9204801e05735377f, prev_block_hash=000000000000000000077b8a2453eb2544db153dcf9d17923b17e6d194a50934)
27/02/2021 23:25:14 [Watcher] New block received  (block_hash=0000000000000000000745d736aa6e6d548d17006aaa84a9204801e05735377f, prev_block_hash=000000000000000000077b8a2453eb2544db153dcf9d17923b17e6d194a50934)
27/02/2021 23:25:36 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000bddacd380e2d85146dbba5ae2954a31a9ff3e32ae1ad3)
27/02/2021 23:25:36 [Responder] New block received  (block_hash=0000000000000000000bddacd380e2d85146dbba5ae2954a31a9ff3e32ae1ad3, prev_block_hash=0000000000000000000745d736aa6e6d548d17006aaa84a9204801e05735377f)
27/02/2021 23:25:36 [Watcher] New block received  (block_hash=0000000000000000000bddacd380e2d85146dbba5ae2954a31a9ff3e32ae1ad3, prev_block_hash=0000000000000000000745d736aa6e6d548d17006aaa84a9204801e05735377f)
27/02/2021 23:54:08 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c03f035c13f6de01236875ff96d121ac177396b3899f5)
27/02/2021 23:54:08 [Responder] New block received  (block_hash=0000000000000000000c03f035c13f6de01236875ff96d121ac177396b3899f5, prev_block_hash=0000000000000000000bddacd380e2d85146dbba5ae2954a31a9ff3e32ae1ad3)
27/02/2021 23:54:08 [Watcher] New block received  (block_hash=0000000000000000000c03f035c13f6de01236875ff96d121ac177396b3899f5, prev_block_hash=0000000000000000000bddacd380e2d85146dbba5ae2954a31a9ff3e32ae1ad3)
28/02/2021 00:14:58 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000766eaffd467cc9a5c54d740ddf3c11283bc76f5dcd279)
28/02/2021 00:14:58 [Responder] New block received  (block_hash=0000000000000000000766eaffd467cc9a5c54d740ddf3c11283bc76f5dcd279, prev_block_hash=0000000000000000000c03f035c13f6de01236875ff96d121ac177396b3899f5)
28/02/2021 00:14:58 [Watcher] New block received  (block_hash=0000000000000000000766eaffd467cc9a5c54d740ddf3c11283bc76f5dcd279, prev_block_hash=0000000000000000000c03f035c13f6de01236875ff96d121ac177396b3899f5)
28/02/2021 00:33:00 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000007b619218d276894e8768876fd42f81131a98dc000da77)
28/02/2021 00:33:00 [Responder] New block received  (block_hash=00000000000000000007b619218d276894e8768876fd42f81131a98dc000da77, prev_block_hash=0000000000000000000766eaffd467cc9a5c54d740ddf3c11283bc76f5dcd279)
28/02/2021 00:33:00 [Watcher] New block received  (block_hash=00000000000000000007b619218d276894e8768876fd42f81131a98dc000da77, prev_block_hash=0000000000000000000766eaffd467cc9a5c54d740ddf3c11283bc76f5dcd279)
28/02/2021 00:55:22 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c428a229a3c23d084cc800002faaff801a5c34edcd837)
28/02/2021 00:55:22 [Responder] New block received  (block_hash=0000000000000000000c428a229a3c23d084cc800002faaff801a5c34edcd837, prev_block_hash=00000000000000000007b619218d276894e8768876fd42f81131a98dc000da77)
28/02/2021 00:55:22 [Watcher] New block received  (block_hash=0000000000000000000c428a229a3c23d084cc800002faaff801a5c34edcd837, prev_block_hash=00000000000000000007b619218d276894e8768876fd42f81131a98dc000da77)
28/02/2021 01:03:04 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000cdd9dfa6b93e9b7e190e23c656b79013e644fb7bbbab3)
28/02/2021 01:03:04 [Responder] New block received  (block_hash=0000000000000000000cdd9dfa6b93e9b7e190e23c656b79013e644fb7bbbab3, prev_block_hash=0000000000000000000c428a229a3c23d084cc800002faaff801a5c34edcd837)
28/02/2021 01:03:04 [Watcher] New block received  (block_hash=0000000000000000000cdd9dfa6b93e9b7e190e23c656b79013e644fb7bbbab3, prev_block_hash=0000000000000000000c428a229a3c23d084cc800002faaff801a5c34edcd837)
28/02/2021 01:05:59 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000ce5008ba21432ae8bc5e3ef1ade5c7a9b810391012643)
28/02/2021 01:05:59 [Responder] New block received  (block_hash=0000000000000000000ce5008ba21432ae8bc5e3ef1ade5c7a9b810391012643, prev_block_hash=0000000000000000000cdd9dfa6b93e9b7e190e23c656b79013e644fb7bbbab3)
28/02/2021 01:05:59 [Watcher] New block received  (block_hash=0000000000000000000ce5008ba21432ae8bc5e3ef1ade5c7a9b810391012643, prev_block_hash=0000000000000000000cdd9dfa6b93e9b7e190e23c656b79013e644fb7bbbab3)
28/02/2021 01:08:40 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000670dd30be6229e99eb13e3b163fa30990f8c3f2a05617)
28/02/2021 01:08:40 [Watcher] New block received  (block_hash=0000000000000000000670dd30be6229e99eb13e3b163fa30990f8c3f2a05617, prev_block_hash=0000000000000000000ce5008ba21432ae8bc5e3ef1ade5c7a9b810391012643)
28/02/2021 01:08:40 [Responder] New block received  (block_hash=0000000000000000000670dd30be6229e99eb13e3b163fa30990f8c3f2a05617, prev_block_hash=0000000000000000000ce5008ba21432ae8bc5e3ef1ade5c7a9b810391012643)
28/02/2021 01:14:31 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000bdcbb5ffe27549ef9c4ee0320aeaea6aad918fbfa6d16)
28/02/2021 01:14:32 [Responder] New block received  (block_hash=0000000000000000000bdcbb5ffe27549ef9c4ee0320aeaea6aad918fbfa6d16, prev_block_hash=0000000000000000000670dd30be6229e99eb13e3b163fa30990f8c3f2a05617)
28/02/2021 01:14:32 [Watcher] New block received  (block_hash=0000000000000000000bdcbb5ffe27549ef9c4ee0320aeaea6aad918fbfa6d16, prev_block_hash=0000000000000000000670dd30be6229e99eb13e3b163fa30990f8c3f2a05617)
28/02/2021 01:37:28 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000015b3cdd37fd72df65a5e846a35bb7e6a9c60b589bf22c)
28/02/2021 01:37:28 [Responder] New block received  (block_hash=000000000000000000015b3cdd37fd72df65a5e846a35bb7e6a9c60b589bf22c, prev_block_hash=0000000000000000000bdcbb5ffe27549ef9c4ee0320aeaea6aad918fbfa6d16)
28/02/2021 01:37:28 [Watcher] New block received  (block_hash=000000000000000000015b3cdd37fd72df65a5e846a35bb7e6a9c60b589bf22c, prev_block_hash=0000000000000000000bdcbb5ffe27549ef9c4ee0320aeaea6aad918fbfa6d16)
28/02/2021 01:39:59 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000087fe6f18a447440cb554ad13bcab19ceaf182849b7cc3)
28/02/2021 01:40:00 [Watcher] New block received  (block_hash=000000000000000000087fe6f18a447440cb554ad13bcab19ceaf182849b7cc3, prev_block_hash=000000000000000000015b3cdd37fd72df65a5e846a35bb7e6a9c60b589bf22c)
28/02/2021 01:40:00 [Responder] New block received  (block_hash=000000000000000000087fe6f18a447440cb554ad13bcab19ceaf182849b7cc3, prev_block_hash=000000000000000000015b3cdd37fd72df65a5e846a35bb7e6a9c60b589bf22c)
28/02/2021 02:08:56 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000009a997551d19d2d4aabe245f7ffabea5d2e8425e6aef78)
28/02/2021 02:08:56 [Watcher] New block received  (block_hash=00000000000000000009a997551d19d2d4aabe245f7ffabea5d2e8425e6aef78, prev_block_hash=000000000000000000087fe6f18a447440cb554ad13bcab19ceaf182849b7cc3)
28/02/2021 02:08:56 [Responder] New block received  (block_hash=00000000000000000009a997551d19d2d4aabe245f7ffabea5d2e8425e6aef78, prev_block_hash=000000000000000000087fe6f18a447440cb554ad13bcab19ceaf182849b7cc3)
28/02/2021 02:09:28 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000000f5a0080335e00891b96c5db64313e8d116728437fa29)
28/02/2021 02:09:28 [Responder] New block received  (block_hash=00000000000000000000f5a0080335e00891b96c5db64313e8d116728437fa29, prev_block_hash=00000000000000000009a997551d19d2d4aabe245f7ffabea5d2e8425e6aef78)
28/02/2021 02:09:28 [Watcher] New block received  (block_hash=00000000000000000000f5a0080335e00891b96c5db64313e8d116728437fa29, prev_block_hash=00000000000000000009a997551d19d2d4aabe245f7ffabea5d2e8425e6aef78)
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/threading.py", line 950, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.9/threading.py", line 888, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/local/lib/python3.9/site-packages/teos/chain_monitor.py", line 123, in monitor_chain_polling
    current_tip = self.block_processor.get_best_block_hash()
  File "/usr/local/lib/python3.9/site-packages/teos/block_processor.py", line 62, in get_best_block_hash
    block_hash = bitcoin_cli(self.btc_connect_params).getbestblockhash()
  File "/usr/local/lib/python3.9/site-packages/teos/utils/auth_proxy.py", line 151, in __call__
    response, status = self._request("POST", self.__url.path, postdata.encode("utf-8"))
  File "/usr/local/lib/python3.9/site-packages/teos/utils/auth_proxy.py", line 114, in _request
    self.__conn.request(method, path, postdata, headers)
  File "/usr/local/lib/python3.9/http/client.py", line 1255, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1301, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1250, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.9/http/client.py", line 1010, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.9/http/client.py", line 950, in send
    self.connect()
  File "/usr/local/lib/python3.9/http/client.py", line 921, in connect
    self.sock = self._create_connection(
  File "/usr/local/lib/python3.9/socket.py", line 843, in create_connection
    raise err
  File "/usr/local/lib/python3.9/socket.py", line 831, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
28/02/2021 02:13:42 [Daemon] Tower identity found. Loading keys
28/02/2021 02:13:42 [Daemon] tower_id = 026247def18440eb3a3e59be829b7c12dd2e86da6989b88644de306132adf72761
28/02/2021 02:13:44 [Daemon] Starting TEOS
28/02/2021 02:13:45 [Daemon] Fresh bootstrap
28/02/2021 02:13:45 [Daemon] Internal API initialized. Serving at localhost:50051
28/02/2021 02:13:45 [RPC] Initialized. Serving at localhost:8814
[2021-02-28 02:13:46 +0000] [30] [INFO] Starting gunicorn 20.0.4
[2021-02-28 02:13:46 +0000] [30] [INFO] Listening at: http://<IP_ADDRESS>:9814 (30)
[2021-02-28 02:13:46 +0000] [30] [INFO] Using worker: sync
[2021-02-28 02:13:46 +0000] [36] [INFO] Booting worker with pid: 36
28/02/2021 02:13:46 [API] Initialized. Serving at <IP_ADDRESS>:9814
28/02/2021 02:18:01 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000ba5232523408775fd70b9d731200267e6d36073b9186f)
28/02/2021 02:18:01 [Responder] New block received  (block_hash=0000000000000000000ba5232523408775fd70b9d731200267e6d36073b9186f, prev_block_hash=00000000000000000000f5a0080335e00891b96c5db64313e8d116728437fa29)
28/02/2021 02:18:01 [Watcher] New block received  (block_hash=0000000000000000000ba5232523408775fd70b9d731200267e6d36073b9186f, prev_block_hash=00000000000000000000f5a0080335e00891b96c5db64313e8d116728437fa29)
28/02/2021 02:19:10 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000434a0210f460be762de3a65b79517b9d537a8b10c4c71)
28/02/2021 02:19:10 [Responder] New block received  (block_hash=0000000000000000000434a0210f460be762de3a65b79517b9d537a8b10c4c71, prev_block_hash=0000000000000000000ba5232523408775fd70b9d731200267e6d36073b9186f)
28/02/2021 02:19:10 [Watcher] New block received  (block_hash=0000000000000000000434a0210f460be762de3a65b79517b9d537a8b10c4c71, prev_block_hash=0000000000000000000ba5232523408775fd70b9d731200267e6d36073b9186f)
28/02/2021 02:43:49 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000136c6998cad74e2252c6295a0969fc250168e1fe78650)
28/02/2021 02:43:49 [Watcher] New block received  (block_hash=0000000000000000000136c6998cad74e2252c6295a0969fc250168e1fe78650, prev_block_hash=0000000000000000000434a0210f460be762de3a65b79517b9d537a8b10c4c71)
28/02/2021 02:43:49 [Responder] New block received  (block_hash=0000000000000000000136c6998cad74e2252c6295a0969fc250168e1fe78650, prev_block_hash=0000000000000000000434a0210f460be762de3a65b79517b9d537a8b10c4c71)
28/02/2021 02:49:31 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000001a6277192705cdf28da247c64bd942d261f944a923d85)
28/02/2021 02:49:31 [Watcher] New block received  (block_hash=00000000000000000001a6277192705cdf28da247c64bd942d261f944a923d85, prev_block_hash=0000000000000000000136c6998cad74e2252c6295a0969fc250168e1fe78650)
28/02/2021 02:49:31 [Responder] New block received  (block_hash=00000000000000000001a6277192705cdf28da247c64bd942d261f944a923d85, prev_block_hash=0000000000000000000136c6998cad74e2252c6295a0969fc250168e1fe78650)
28/02/2021 02:50:41 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000012dfc019be41ebffb805d43561327d667764e677c06e)
28/02/2021 02:50:41 [Watcher] New block received  (block_hash=0000000000000000000012dfc019be41ebffb805d43561327d667764e677c06e, prev_block_hash=00000000000000000001a6277192705cdf28da247c64bd942d261f944a923d85)
28/02/2021 02:50:41 [Responder] New block received  (block_hash=0000000000000000000012dfc019be41ebffb805d43561327d667764e677c06e, prev_block_hash=00000000000000000001a6277192705cdf28da247c64bd942d261f944a923d85)
28/02/2021 02:52:38 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000005f1b6b247dfaa6f6856686ae527b4ed0781ba18024daf)
28/02/2021 02:52:38 [Watcher] New block received  (block_hash=00000000000000000005f1b6b247dfaa6f6856686ae527b4ed0781ba18024daf, prev_block_hash=0000000000000000000012dfc019be41ebffb805d43561327d667764e677c06e)
28/02/2021 02:52:38 [Responder] New block received  (block_hash=00000000000000000005f1b6b247dfaa6f6856686ae527b4ed0781ba18024daf, prev_block_hash=0000000000000000000012dfc019be41ebffb805d43561327d667764e677c06e)
28/02/2021 03:01:05 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000004af116f2d8b8ae5d0e4e903bc66b5e69cd8ff58ff7b0)
28/02/2021 03:01:05 [Responder] New block received  (block_hash=000000000000000000004af116f2d8b8ae5d0e4e903bc66b5e69cd8ff58ff7b0, prev_block_hash=00000000000000000005f1b6b247dfaa6f6856686ae527b4ed0781ba18024daf)
28/02/2021 03:01:05 [Watcher] New block received  (block_hash=000000000000000000004af116f2d8b8ae5d0e4e903bc66b5e69cd8ff58ff7b0, prev_block_hash=00000000000000000005f1b6b247dfaa6f6856686ae527b4ed0781ba18024daf)
28/02/2021 03:19:30 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000001c526e814d73a729d98ada0874ba1f2c8da8a6e3b5cf2)
28/02/2021 03:19:30 [Watcher] New block received  (block_hash=00000000000000000001c526e814d73a729d98ada0874ba1f2c8da8a6e3b5cf2, prev_block_hash=000000000000000000004af116f2d8b8ae5d0e4e903bc66b5e69cd8ff58ff7b0)
28/02/2021 03:19:30 [Responder] New block received  (block_hash=00000000000000000001c526e814d73a729d98ada0874ba1f2c8da8a6e3b5cf2, prev_block_hash=000000000000000000004af116f2d8b8ae5d0e4e903bc66b5e69cd8ff58ff7b0)
28/02/2021 03:20:01 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000095ee2df60c299445cb226536a993a162781ecf5a70fcc)
28/02/2021 03:20:01 [Responder] New block received  (block_hash=000000000000000000095ee2df60c299445cb226536a993a162781ecf5a70fcc, prev_block_hash=00000000000000000001c526e814d73a729d98ada0874ba1f2c8da8a6e3b5cf2)
28/02/2021 03:20:01 [Watcher] New block received  (block_hash=000000000000000000095ee2df60c299445cb226536a993a162781ecf5a70fcc, prev_block_hash=00000000000000000001c526e814d73a729d98ada0874ba1f2c8da8a6e3b5cf2)
28/02/2021 03:21:08 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000046547ec9b1e8fe05446add5b0e54cab4222e85b02f087)
28/02/2021 03:21:08 [Responder] New block received  (block_hash=000000000000000000046547ec9b1e8fe05446add5b0e54cab4222e85b02f087, prev_block_hash=000000000000000000095ee2df60c299445cb226536a993a162781ecf5a70fcc)
28/02/2021 03:21:08 [Watcher] New block received  (block_hash=000000000000000000046547ec9b1e8fe05446add5b0e54cab4222e85b02f087, prev_block_hash=000000000000000000095ee2df60c299445cb226536a993a162781ecf5a70fcc)
28/02/2021 03:40:32 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000abcd2c9949ffe2363d83f56a041cf31a8dd74af7d9882)
28/02/2021 03:40:32 [Responder] New block received  (block_hash=0000000000000000000abcd2c9949ffe2363d83f56a041cf31a8dd74af7d9882, prev_block_hash=000000000000000000046547ec9b1e8fe05446add5b0e54cab4222e85b02f087)
28/02/2021 03:40:32 [Watcher] New block received  (block_hash=0000000000000000000abcd2c9949ffe2363d83f56a041cf31a8dd74af7d9882, prev_block_hash=000000000000000000046547ec9b1e8fe05446add5b0e54cab4222e85b02f087)
28/02/2021 03:56:06 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000043d68823c5a8e6f5a7f62e4e04456ed4ad87a8b81bce4)
28/02/2021 03:56:07 [Responder] New block received  (block_hash=000000000000000000043d68823c5a8e6f5a7f62e4e04456ed4ad87a8b81bce4, prev_block_hash=0000000000000000000abcd2c9949ffe2363d83f56a041cf31a8dd74af7d9882)
28/02/2021 03:56:07 [Watcher] New block received  (block_hash=000000000000000000043d68823c5a8e6f5a7f62e4e04456ed4ad87a8b81bce4, prev_block_hash=0000000000000000000abcd2c9949ffe2363d83f56a041cf31a8dd74af7d9882)
28/02/2021 03:57:59 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000048bdea371aed1061bf0aea904a3a7f4e5c09e354e6951)
28/02/2021 03:57:59 [Watcher] New block received  (block_hash=000000000000000000048bdea371aed1061bf0aea904a3a7f4e5c09e354e6951, prev_block_hash=000000000000000000043d68823c5a8e6f5a7f62e4e04456ed4ad87a8b81bce4)
28/02/2021 03:57:59 [Responder] New block received  (block_hash=000000000000000000048bdea371aed1061bf0aea904a3a7f4e5c09e354e6951, prev_block_hash=000000000000000000043d68823c5a8e6f5a7f62e4e04456ed4ad87a8b81bce4)
28/02/2021 04:00:12 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000c1154f8cb93095428a2e9f7c07022539ddc826d239134)
28/02/2021 04:00:12 [Watcher] New block received  (block_hash=0000000000000000000c1154f8cb93095428a2e9f7c07022539ddc826d239134, prev_block_hash=000000000000000000048bdea371aed1061bf0aea904a3a7f4e5c09e354e6951)
28/02/2021 04:00:12 [Responder] New block received  (block_hash=0000000000000000000c1154f8cb93095428a2e9f7c07022539ddc826d239134, prev_block_hash=000000000000000000048bdea371aed1061bf0aea904a3a7f4e5c09e354e6951)
28/02/2021 04:34:39 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000cd9173e22e0eaaf82621c68d5fd758aa938e23bbf6e65)
28/02/2021 04:34:39 [Responder] New block received  (block_hash=0000000000000000000cd9173e22e0eaaf82621c68d5fd758aa938e23bbf6e65, prev_block_hash=0000000000000000000c1154f8cb93095428a2e9f7c07022539ddc826d239134)
28/02/2021 04:34:39 [Watcher] New block received  (block_hash=0000000000000000000cd9173e22e0eaaf82621c68d5fd758aa938e23bbf6e65, prev_block_hash=0000000000000000000c1154f8cb93095428a2e9f7c07022539ddc826d239134)
28/02/2021 04:49:57 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000033a358a3fa1614e9cb1047638fc5c5acd5ffd047dede2)
28/02/2021 04:49:57 [Watcher] New block received  (block_hash=000000000000000000033a358a3fa1614e9cb1047638fc5c5acd5ffd047dede2, prev_block_hash=0000000000000000000cd9173e22e0eaaf82621c68d5fd758aa938e23bbf6e65)
28/02/2021 04:49:57 [Responder] New block received  (block_hash=000000000000000000033a358a3fa1614e9cb1047638fc5c5acd5ffd047dede2, prev_block_hash=0000000000000000000cd9173e22e0eaaf82621c68d5fd758aa938e23bbf6e65)
28/02/2021 04:53:04 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000b20cf49764981714c5251c3c58fcd567af6e6b8262596)
28/02/2021 04:53:04 [Watcher] New block received  (block_hash=0000000000000000000b20cf49764981714c5251c3c58fcd567af6e6b8262596, prev_block_hash=000000000000000000033a358a3fa1614e9cb1047638fc5c5acd5ffd047dede2)
28/02/2021 04:53:05 [Responder] New block received  (block_hash=0000000000000000000b20cf49764981714c5251c3c58fcd567af6e6b8262596, prev_block_hash=000000000000000000033a358a3fa1614e9cb1047638fc5c5acd5ffd047dede2)
28/02/2021 05:40:08 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000003e82cd3154f5e7f9e47431c28e6f2af4f0c93eab28b)
28/02/2021 05:40:08 [Watcher] New block received  (block_hash=0000000000000000000003e82cd3154f5e7f9e47431c28e6f2af4f0c93eab28b, prev_block_hash=0000000000000000000b20cf49764981714c5251c3c58fcd567af6e6b8262596)
28/02/2021 05:40:08 [Responder] New block received  (block_hash=0000000000000000000003e82cd3154f5e7f9e47431c28e6f2af4f0c93eab28b, prev_block_hash=0000000000000000000b20cf49764981714c5251c3c58fcd567af6e6b8262596)
28/02/2021 05:52:43 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000057edf6958bc7afad1e8cc5b432a932a29151d75b82744)
28/02/2021 05:52:43 [Responder] New block received  (block_hash=000000000000000000057edf6958bc7afad1e8cc5b432a932a29151d75b82744, prev_block_hash=0000000000000000000003e82cd3154f5e7f9e47431c28e6f2af4f0c93eab28b)
28/02/2021 05:52:43 [Watcher] New block received  (block_hash=000000000000000000057edf6958bc7afad1e8cc5b432a932a29151d75b82744, prev_block_hash=0000000000000000000003e82cd3154f5e7f9e47431c28e6f2af4f0c93eab28b)
28/02/2021 06:30:25 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000091c2e41bc41f49c2a4fc30dc42ff43d07021c62844af4)
28/02/2021 06:30:25 [Watcher] New block received  (block_hash=000000000000000000091c2e41bc41f49c2a4fc30dc42ff43d07021c62844af4, prev_block_hash=000000000000000000057edf6958bc7afad1e8cc5b432a932a29151d75b82744)
28/02/2021 06:30:25 [Responder] New block received  (block_hash=000000000000000000091c2e41bc41f49c2a4fc30dc42ff43d07021c62844af4, prev_block_hash=000000000000000000057edf6958bc7afad1e8cc5b432a932a29151d75b82744)
28/02/2021 06:40:43 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000009a9562775b694776055fa283489e5ee374205069c3bea)
28/02/2021 06:40:43 [Watcher] New block received  (block_hash=00000000000000000009a9562775b694776055fa283489e5ee374205069c3bea, prev_block_hash=000000000000000000091c2e41bc41f49c2a4fc30dc42ff43d07021c62844af4)
28/02/2021 06:40:43 [Responder] New block received  (block_hash=00000000000000000009a9562775b694776055fa283489e5ee374205069c3bea, prev_block_hash=000000000000000000091c2e41bc41f49c2a4fc30dc42ff43d07021c62844af4)
28/02/2021 06:42:38 [ChainMonitor] New block received via zmq  (block_hash=000000000000000000098a2408160d6d96304869470e79668c91aedbd7d5b292)
28/02/2021 06:42:39 [Responder] New block received  (block_hash=000000000000000000098a2408160d6d96304869470e79668c91aedbd7d5b292, prev_block_hash=00000000000000000009a9562775b694776055fa283489e5ee374205069c3bea)
28/02/2021 06:42:39 [Watcher] New block received  (block_hash=000000000000000000098a2408160d6d96304869470e79668c91aedbd7d5b292, prev_block_hash=00000000000000000009a9562775b694776055fa283489e5ee374205069c3bea)
28/02/2021 06:44:51 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000000446eaefee1ae3c7a02f1a97570253123580a02ce15a1)
28/02/2021 06:44:51 [Responder] New block received  (block_hash=00000000000000000000446eaefee1ae3c7a02f1a97570253123580a02ce15a1, prev_block_hash=000000000000000000098a2408160d6d96304869470e79668c91aedbd7d5b292)
28/02/2021 06:44:51 [Watcher] New block received  (block_hash=00000000000000000000446eaefee1ae3c7a02f1a97570253123580a02ce15a1, prev_block_hash=000000000000000000098a2408160d6d96304869470e79668c91aedbd7d5b292)
28/02/2021 07:05:54 [ChainMonitor] New block received via zmq  (block_hash=0000000000000000000400a19ea3becf6f9e665e195980155f486ee557397e4e)
28/02/2021 07:05:54 [Responder] New block received  (block_hash=0000000000000000000400a19ea3becf6f9e665e195980155f486ee557397e4e, prev_block_hash=00000000000000000000446eaefee1ae3c7a02f1a97570253123580a02ce15a1)
28/02/2021 07:05:54 [Watcher] New block received  (block_hash=0000000000000000000400a19ea3becf6f9e665e195980155f486ee557397e4e, prev_block_hash=00000000000000000000446eaefee1ae3c7a02f1a97570253123580a02ce15a1)
28/02/2021 07:08:24 [ChainMonitor] New block received via zmq  (block_hash=00000000000000000006f1ffe4aa24dce7f239e35a078692b65bf592b4b51949)
28/02/2021 07:08:24 [Responder] New block received  (block_hash=00000000000000000006f1ffe4aa24dce7f239e35a078692b65bf592b4b51949, prev_block_hash=0000000000000000000400a19ea3becf6f9e665e195980155f486ee557397e4e)
28/02/2021 07:08:24 [Watcher] New block received  (block_hash=0

Looks like there's some kind of connection problem between the tower and bitcoind. Let me look into it and see if I can figure out what's going on.

27/02/2021 16:01:33 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:33 [Daemon] ERROR: An error occurred: Cannot connect to bitcoind. Shutting down
27/02/2021 16:01:37 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:41 [Daemon] Tower identity found. Loading keys
27/02/2021 16:01:33 [Daemon] ERROR: An error occurred: Cannot connect to bitcoind. Shutting down

This first bit (I'm assuming the initial bootstrap) happens because bitcoind is not still launched (or at least accesible via RPC), so the teos container is keeping restarting until it gets to connect to bitcoind.

Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/threading.py", line 950, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.9/threading.py", line 888, in run
self._target(*self._args, **self._kwargs)
File "/usr/local/lib/python3.9/site-packages/teos/chain_monitor.py", line 123, in monitor_chain_polling
current_tip = self.block_processor.get_best_block_hash()
File "/usr/local/lib/python3.9/site-packages/teos/block_processor.py", line 62, in get_best_block_hash
block_hash = bitcoin_cli(self.btc_connect_params).getbestblockhash()
File "/usr/local/lib/python3.9/site-packages/teos/utils/auth_proxy.py", line 151, in call
response, status = self._request("POST", self.__url.path, postdata.encode("utf-8"))
File "/usr/local/lib/python3.9/site-packages/teos/utils/auth_proxy.py", line 114, in _request
self.__conn.request(method, path, postdata, headers)
File "/usr/local/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/local/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/local/lib/python3.9/http/client.py", line 921, in connect
self.sock = self._create_connection(
File "/usr/local/lib/python3.9/socket.py", line 843, in create_connection
raise err
File "/usr/local/lib/python3.9/socket.py", line 831, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

This second bit happens because of the same reason, but this time while teos is running. Can you check if the bitcoind container is restarting from time to time?
This is realted to #19 though. teos should halt and keep polling bitcoind if the later goes down. bitcoind is really stable though, so it crashing is something quite strange.

so I am using standard dockerized deployent, all services look normal, none have or report issues. Anything in specific should I provide? I could get you access to the server if you wish, its a testing pre production server, if you think could help debug faster. hence like mentioned this is a clean dockerized version nothing changed.

I can give it a look if you give me access. Drop me an email at<EMAIL_ADDRESS>

@sr-gi email sent.

Hi @sr-gi we have a downtime due to the OVH DC Fire. No Data loss involved, yet this downtime...

Oh OK. Can you ping me when the server is back online so I can patch this?

ofcourse I will do so.


Adding performer

Adding performer to the genomic analysis.
output.zip file is updated accordingly.
Device is one of the possible options of the performer element. Also, there is a separate element for device. This may be a point for review and discussion.

Let's discuss how to best handle the "performer" requirement. We need to think about who or what will be doing the performing as well as what level within the resource the attribute should be added.


Auto burn feature

Clear and concise description of the problem
This feature will help control IBXC circulation.
Suggested solution
The auto burn mechanism will reduce supply and eventually stop when supply falls below a defined amount.
Alternative
This feature will improve transparency and predictability
Additional context
Thanks
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

The problem does not apply with IBAX, where the supply is fixed; it is the non-fixed supply that has to be considered for the combustion mechanism.


Allow triggering Touch Bar customization

It would be helpful to have a function that invokes Touch Bar customization, as seen in native apps' View –> Customize Touch Bar... menu.

Good suggestion. Will look in to this
(https://developer.apple.com/documentation/appkit/nstouchbar?language=objc#2647080)


Support avatar field in create and update method of the topic service

@svanharmelen is something like that implemented already somewhere here in the library?

@svanharmelen It should be properly implemented now. I've also added an example which "works on my machine ™). Maybe you can verify?

@svanharmelen would be nice to have this in the next release 🎉

@timofurrer I added a commit wit a few changes. I tested what the requests look like in different situations and it all looks good. But probably good if you can confirm/test it against a running instance?

@svanharmelen at least running the example works as expected 👍


Error while trying to install package pyhepmc-ng

Running pip install heparchy produces the following error on MacOS version 12.3.1 with Apple M1 Pro chip:
Building wheels for collected packages: pyhepmc-ng
Building wheel for pyhepmc-ng (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [18 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.macosx-10.9-x86_64-cpython-38
creating build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/_version.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/_io.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/init.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/view.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
running build_ext
building 'pyhepmc_ng._bindings' extension
creating build/temp.macosx-10.9-x86_64-cpython-38
creating build/temp.macosx-10.9-x86_64-cpython-38/extern
creating build/temp.macosx-10.9-x86_64-cpython-38/extern/HepMC3
creating build/temp.macosx-10.9-x86_64-cpython-38/extern/HepMC3/src
creating build/temp.macosx-10.9-x86_64-cpython-38/src
error: [Errno 2] No such file or directory: 'x86_64-apple-darwin13.4.0-clang'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pyhepmc-ng
Running setup.py clean for pyhepmc-ng
Failed to build pyhepmc-ng
Installing collected packages: pyhepmc-ng, h5py, heparchy
Running setup.py install for pyhepmc-ng ... error
error: subprocess-exited-with-error
× Running setup.py install for pyhepmc-ng did not run successfully.
│ exit code: 1
╰─> [20 lines of output]
running install
/Users/kieran/opt/anaconda3/envs/tree_extractor/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
running build
running build_py
creating build
creating build/lib.macosx-10.9-x86_64-cpython-38
creating build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/_version.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/_io.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/init.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
copying src/pyhepmc_ng/view.py -> build/lib.macosx-10.9-x86_64-cpython-38/pyhepmc_ng
running build_ext
building 'pyhepmc_ng._bindings' extension
creating build/temp.macosx-10.9-x86_64-cpython-38
creating build/temp.macosx-10.9-x86_64-cpython-38/extern
creating build/temp.macosx-10.9-x86_64-cpython-38/extern/HepMC3
creating build/temp.macosx-10.9-x86_64-cpython-38/extern/HepMC3/src
creating build/temp.macosx-10.9-x86_64-cpython-38/src
error: [Errno 2] No such file or directory: 'x86_64-apple-darwin13.4.0-clang'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> pyhepmc-ng
note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
Versions
Python: 3.8.13
Further Information
pip install pyhepmc runs successfully, the authors of  pyhepmc state "The pyhepmc-ng package is continued as the package pyhepmc. Please install pyhepmc, pyhepmc-ng is no longer updated.", perhaps this is the issue?

Thanks for this @Kieran-Mg1! Will test the newly maintained package with the heparchy.read.hepmc module. I suspect there will at least be some minor namespace errors if I only change the dependency, but this module does need to be updated to match the HDF5 interface anyway, so some maintenance is in order one way or another.
Will try to get something working online today, but if not will be early next week.

So switching the dependency indeed break that module's functionality in some nontrivial ways, and some time spent working out the differences between the API of pyhepmc_ng and pyhepmc is necessary. I might just remove the module from the public API while I work on fixing it, and reintroduce it once done.
@Kieran-Mg1 would it be possible for you to see whether installing pyhepmc-ng==0.4.3 before installing heparchy solves the issue? If so, it could be a short term solution that I could pin in the setup.cfg until I change the implementation of heparchy.read.hepmc.

@jacanchaplais your suggested solution worked, installing pyhepmc-ng==0.4.3 before installing heparchy produces no error message and heparchy appears to install successfully.

Not sure if this is related, but from heparchy.read.hdf import HdfReader  produces the error No module named 'heparchy.read.hdf'; 'heparchy.read' is not a package.
When I navigate to where heparchy is installed, listed in the directory is: _init_.py,	_pycache_,	_version.py,	data.py,	hepmc.py,	read.py,		utils.py,	write.py, which I think explains the error.
I installed heparchy with pip install heparchy, is this to be expected?

Thanks for pointing this out, I installed it locally in dev mode, and I think Giorgio did too, so we missed that the subpackages need to explicitly be added to the namespace. I've pushed a patch which should fix both of the problems listed here. Could you try installing it with the following:
pip install git+https://github.com/jacanchaplais/heparchy.git@patch/outdated-deps-15
If that works I'll merge into the release branch, and bump up the beta version to heparchy==0.2b2 on PyPI, then you can install that. :)

Yes pip install git+https://github.com/jacanchaplais/heparchy.git@patch/outdated-deps-15 worked correctly, thank you :)

Excellent, built and uploaded to PyPI. :) Thanks for flagging this!
https://pypi.org/project/heparchy/0.2b2/

Hi Kieran, ah that's intentional! It's because read_event is deprecated. Now you can simply subscript the process object to get event objects, eg.
with HdfReader(data_path) as hep_file:
    proc = hep_file.read_process("default")
    event = proc[2]  # explicit subscripting
    for event in proc:  # iteration
        ...

The main branch should not be used as an up-to-date reference, since it only gets updated when the next major or minor version of the release branch comes out of beta, and gets merged. Until this happens the API should be considered unstable. To be honest, the release branch should be renamed to release/1.0, since there are significant API changes. In any case, I really appreciate you looking into the source code! I do highly recommend that you pin yourself to a version officially distributed on PyPI without custom modifications, for your work, though (since this may prevent you getting downstream improvements or bug fixes).

See #16. Added a new release, heparchy==0.2b3, which includes the read_event method, but adds a deprecation warning to it.


bump postcss-reporter to v2

this is in response to the issue reported here suitcss/stylelint-config-suitcss#24
where running suitcss resulted in lots of noisy "undefined [undefined]" output
the issue was related to message filtering in postcss-reporter
reported here TrySound/postcss-inline-svg#32
and then fixed here postcss/postcss-reporter#30
I've bumped the version and re-run my app and it cleared the issue and did not appear to introduce any new issues

ran the tests locally and they were failing before any changes on a clean pull from master
after the change the same tests continued to fail, doubt they are related

@danalloway thanks for submitting this pr! Do you mind fixing that test?
I don't know why that rule is being moved maybe some other plugin's fault. cc @simonsmith

Looks like tests are broken on master. It's actually a patch release in postcss-import that fixed a long standing import order bug and our tests fail because the fixtures worked against the bug.
Think we just need to adjust our fixture to fix it, and then this PR can be rebased and merged. I'll do that shortly.

Merged #61 @danalloway please pull.

For the future better work in a branch :)

I think git pull --rebase will do the trick but yes, branches ftw

ok, I feel like an idiot but I completely messed up my fork of the repository
had to start over
here is a clean one, from a new branch forked from head with my change #63

updated all deps and still getting undefined [undefined] webpack output

they haven't tagged a release with the changes in it yet, so if you're just trying to get this from NPM it won't have this fix in it.
I have this in my package.json file right now to test it.
"suitcss-preprocessor": "https://github.com/suitcss/preprocessor#531b246ce67baaac3574fba547f298208d8a57e9",

Any update on this? :)

Sorry for the delay :)
We just have two small issues to get fixed and then we're good to go

Ah, great to hear!

3.0.1 has been published and contains this fix. Thanks for the patience :)


Add support for multi-threading

Overview
Monte-Carlo simulation is perfectly suited for parallel processing: it needs to run the same block of code a huge number of times. It looks like Rayon would be a great choice for implementing this feature.
Implementation Notes
I think that most of the library utilities should be good to go for threading, we just need find an efficient way to aggregate the scores. My initial thought would be to have one AggregateScore object per thread, and then periodically merge those back into a shared (Arc) AggregateScore that synchronizes the data across threads.

Can I work on this too ? I wanted to learn about thread handling in rust. :blush:

Sure!   I've not done much with parallelism in rust either, but I've heard
that it is easier to do safely (and it seems like the case from what I read
in the rust book).
On Wed, Jul 12, 2023 at 1:44 PM spoloxs @.***> wrote:

Can I work on this too ? I wanted to learn about thread handling in rust.
😊
—
Reply to this email directly, view it on GitHub
https://github.com/MatthewPeterKelly/poker-stats/issues/7#issuecomment-1632952300,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6CWOOFH2PFNTOQVELZ3FTXP3O65ANCNFSM6AAAAAAZTCWBYY
.
You are receiving this because you authored the thread.Message ID:
@.***>

As part of implementing this feature we should include some unit tests to verify that the results are deterministic (given an appropriate RNG seed) and consistent with the results given by the single-threaded implementation.

Sorry I have been busy for the last few days I will do it in a few days

Sorry I have been busy for the last few days I will do it in a few days

No worries!  Thanks for checking in.

That code looks like it's starting down the right path.  Here is the first architecture that comes to mind.
The user specifies the number of threads (typically the number of cores in the processor). Managing the thread synchronization is expensive, so we would want to batch the calculations. The simplest thing would be, for example, if the user specifies 8000 samples and 8 threads, then we run 1000 samples in each thread with a single join. This is probably the right place to start.
You could also imagine threads "checking in" more frequently, for example, each running 200 samples, then returning the results. This would allow the main thread to operate on intermediate calculations, while the other threads go back to finish the calculation. We don't have a good use case for this yet, so it probably isn't worth the complexity.

what's the need of rng as parameter

Right now, we have the main function grab the thread RNG and pass that into the statistics function. That function wouldn't change, but we would insert another function between it and function that manages the thread synchronization, which would then be called from main. That intermediate layer would manage spawning threads, passing in the right random number generators, and merging results.

I should divide sample_numbers with seeds and then run loop with multiple threads. Finally merging all together.

Yeah, that seems right.
Good luck!

I still don't understand passing threadRng as parameter for aggregatescore can you explain it please.

what does threadrng do?

pub fn sample_aggregate_scores<const N_HAND: usize, R: Rng>(rng: &mut R, num_samples: u32, number_of_threads: u32) -> AggregateScore {
let scores = Arc::new(Mutex::new(AggregateScore::default()));
let num_samples_perthread = num_samples / number_of_threads;
let num_samples_remainder = num_samples % number_of_threads;
let mut handles = vec![];
for _i in 0..number_of_threads - 1 {
for _ in 0..num_samples_perthread {
let scores = Arc::clone(&scores);
let handle = thread::spawn(move ||{
let mut scores_clone = scores.lock().unwrap();
scores_clone.insert(&HandScore::from(&HandStats::from(&Hand::<N_HAND>::draw(
&mut rand::thread_rng()
))));
}
);
handles.push(handle);
}
}
for _ in 0..num_samples_remainder {
let scores = Arc::clone(&scores);
let handle = thread::spawn(move ||{
let mut scores_clone = scores.lock().unwrap();
scores_clone.insert(&HandScore::from(&HandStats::from(&Hand::<N_HAND>::draw(
&mut rand::thread_rng()
))));
}
);
handles.push(handle);
}
for handle in handles{
handle.join().unwrap();
}
return Arc::into_inner(scores).unwrap().into_inner().unwrap()
}
I coded it like this but rng was never used. I cannot move rng either I have to use arc and mutex for it then create clone of it just like scores

I raised PR check if that works according to your requirement

I cannot move rng either I have to use arc and mutex for it then create clone of it just like scores.

I added some comments in your PR that should address. Let me know if it is clear now.  Good luck!


WIP: Switch from tools/node to node

This PR removes tools/node and replaces calls to this script with node.
This is to fix #2409

Automated message from Dropbox CLA bot
@arpith, it looks like you've already signed the Dropbox CLA. Thanks!

@rishig @umairwaheed: does this fix your issue?
@showell @timabbott: does anything else need to be done?

Works for me!

Looks good to me, but for this particular change, we don't actually need to bump the PROVISION_VERSION, since it doesn't require users to re-provision.  I believe we have that change on another branch, anyway.

Merged, thanks @arpith!  (After removing the PROVISION_VERSION bump, which came automatically since we'd already merged moving it to 2.3)

Thanks @timabbott!


[upstream-carry] align to 4.13.0 content

Align the 4.12 branch with the NRT changes landed in 4.13.
Minimal PR with only the NRT related changes with no extra changes.

xref: https://github.com/openshift-kni/scheduler-plugins/pull/100 for docs about the carry process


Integrate a chatbot

Current Behavior
There are no chatbots on the website
Desired Behavior
Integrate a chatbot with a floating action button that makes the chatbot popup, you can use dialogflow API or tools of your choice

assgin me.

Done

@Aashish-cyber are you working on this ?

Yeah,, I am working on it, actually it's my first contribution to open
source so and i am making this chat bot using dialogue flow API,,
On Tue, 5 Oct, 2021, 8:58 pm Sandeep Rajakrishnan, @.***>
wrote:

@Aashish-cyber https://github.com/Aashish-cyber are you working on this
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sudhay23/ShopOnline-Web-App/issues/60#issuecomment-934513705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANWAS6E4ITN6VIANJSSE7VTUFMKRXANCNFSM5FF5755A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Ohh alright

the remote origin should be your fork of this repo


Debugger doesn't stop at breakpoints in VScode

Hey, I followed few guides, all of them are basically like the one below.
https://github.com/vincedgy/aws-sam-webpack-typescript
and I also cloned the finished project to try out to debug
https://github.com/vincedgy/aws-sam-webpack-typescript/tree/master/demo
I have also tried to follow your instructions to run debugger for vscode/typescript.
None of which I got the debugger to stop at the breakpoints.
I can see in the console log that debugger got attached. It initially stop at the bootstrap file, but after that it just runs through without stopping on any breakpoints which I've  set.

$ sam local invoke -d 5858 -e events/event.json HelloWorldFunction
C:\Program Files\Amazon\AWSSAMCLI\runtime\lib\site-packages\chevron\renderer.py:73: SyntaxWarning: "is" with a literal. Did you mean "=="?
if scope is 0:
Invoking app.lambdaHandler (nodejs12.x)
Skip pulling image and use local one: amazon/aws-sam-cli-emulation-image-nodejs12.x:rapid-1.9.0.
Mounting E:\Documents\Development\aws\aws-typescript.aws-sam\build\HelloWorldFunction as /var/task:ro,delegated inside runtime container
Debugger attached.
←[32mSTART RequestId: e0624f01-7b96-148c-27d4-d8c700e91db3 Version: $LATEST←[0m
2020-11-18T22:51:38.640Z        e0624f01-7b96-148c-27d4-d8c700e91db3    INFO    Hello World
2020-11-18T22:51:38.641Z        e0624f01-7b96-148c-27d4-d8c700e91db3    INFO    { statusCode: 200, body: '{"message":"hello world"}' }
←[32mEND RequestId: e0624f01-7b96-148c-27d4-d8c700e91db3←[0m
←[32mREPORT RequestId: e0624f01-7b96-148c-27d4-d8c700e91db3     Init Duration: 355278.73 ms     Duration: 4.00 ms       Billed Duration:
100 ms  Memory Size: 128 MB     Max Memory Used: 51 MB  ←[0m
{"statusCode":200,"body":"{"message":"hello world"}"}

I'm using
sam-cli 1.9.0
vscode 1.51
I'm not sure if I perhaps missing something. Maybe the following part where you mentioned source map support
https://github.com/graphboss/aws-sam-webpack-plugin#source-map-support
I'm not entirely sure how to set it, so I just applied it as global environment variable.
Any advice or suggestion would be really helpful.

I got debugger to work for Javascript files with the following launch configuration
	{
		"type": "aws-sam",
		"request": "direct-invoke",
		"name": "sam-with-webpack-typescript",
		"invokeTarget": {
			"target": "code",
			"projectRoot": "sam-with-webpack-typescript",
			"lambdaHandler": "src/hello-world/app.lambdaHandler"
		},
		"lambda": {
			"runtime": "nodejs12.x",
			"payload": {},
			"environmentVariables": {}
		}
	},

Which also requires you to install AWS Toolkit first for VScode. However with that it still cannot recognize breakpoints in Typescript files.

If someone else have issue with debugger doesn't work out of the box, I have found solution for it.
In my case, when running this on a Windows 10 machine.
One way is to use debugger in the code.
The other solution is in the generated launcher add cwd and write the path to the project folder

Im also having issues with this. I can' t seem to get debugging to work for the life of me.

Im also having issues with this. I can' t seem to get debugging to work for the life of me.

@dm430 for me it ended up being related to the function code itself; as soon as I dropped a console log statement it seemed to be able to debug from that point forward

@dm430 for me it ended up being related to the function code itself; as soon as I dropped a console log statement it seemed to be able to debug from that point forward

@ryansonshine I wish that was the fix for me. Ive tried everything that I can thing of, but can not get vscode or chrome inspector to stop at break points set in the actual source files. I am able to step into the compiled code, but thats useless.

@ryansonshine I wish that was the fix for me. Ive tried everything that I can thing of, but can not get vscode or chrome inspector to stop at break points set in the actual source files. I am able to step into the compiled code, but thats useless.

I believe you have to run with the node environment variable set to development. Try running "NODE_ENV=development npm run-script watch" and then trying the debugger.
For me, if I don't set the env variable I get the same issues as you.

After some experimenting I think the problem is also related to the tsconfig.json. I've updated the README and have a working example at aws-sam-webpack-demo.

Circling back on this issue. Debugging breaks on the latest version of vscode (1.60.0). Verified with the demo. Version 1.59.1 works debugging works just fine.

@AndrewZelaya I've created a new issue for fixing debugging in VS Code 1.60.0. See #66


Make quick-start failing with permissions error while setting up ansible

Make quick-start fails while setting up ansible saying the location /openwhisk/ansible/environments/local not writeable.  can anyone suggest on it?
sudo make quick-start
Password:
Downloading source tar ball....
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   134    0   134    0     0     99      0 --:--:--  0:00:01 --:--:--    99
100 10.3M  100 10.3M    0     0   194k      0  0:00:54  0:00:54 --:--:--  346k
Unpacking tarball.
downloading the CLI tool ...
downloading cli for mac
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   624    0   624    0     0    399      0 --:--:--  0:00:01 --:--:--   399
100 3353k  100 3353k    0     0   106k      0  0:00:31  0:00:31 --:--:--  196k
Archive:  wsk.zip
  inflating: wsk
  inflating: NOTICE.txt
  inflating: README.md
  inflating: LICENSE.txt
pulling the docker images short list...
Using default tag: latest
latest: Pulling from openwhisk/controller
Digest: sha256:8da80cc2b7f8e1f5bca6738e0ef30c73b27534d25ec9caa8aa9276b5d657e153
Status: Image is up to date for openwhisk/controller:latest
Using default tag: latest
latest: Pulling from openwhisk/invoker
Digest: sha256:71747d44e27fd8f59c0eff408462e603da2cbb2708c706ce3759ab38b090c14d
Status: Image is up to date for openwhisk/invoker:latest
Using default tag: latest
latest: Pulling from openwhisk/nodejs6action
Digest: sha256:5b01e6dc86128c3579b86abbb4630d70127e5438ccd4ab9b2e1ea9ebb3b81359
Status: Image is up to date for openwhisk/nodejs6action:latest
Using default tag: latest
latest: Pulling from openwhisk/dockerskeleton
Digest: sha256:0f6510dca44afe8bd7d6159e54d491a8881686e51f107afa7cd87c925d56e034
Status: Image is up to date for openwhisk/dockerskeleton:latest
host ip address: <IP_ADDRESS>
checking required ports ...
 ... OK
  ... preparing api-gateway configuration
Starting openwhisk_minio_1 ... done
<?xml version="1.0" encoding="UTF-8"?>
<Error>AccessDenied<Message>Access Denied.</Message><Key></Key><BucketName></BucketName><Resource>/</Resource><RequestId>3L137</RequestId><HostId>3L137</HostId></Error>generating server certificate request
generating self-signed password-less server certificate
Signature ok
subject=/C=US/ST=NY/L=Yorktown/O=OpenWhisk/CN=<IP_ADDRESS>
Getting Private key
generate keystore
waiting for the database to come up ... on <IP_ADDRESS>
.Starting openwhisk_zookeeper_1 ...

 [WARNING]: Unable to parse /openwhisk/ansible/environments/local as an inventory source

 [WARNING]: No inventory was parsed, only implicit localhost is available

 [WARNING]: Could not match supplied host pattern, ignoring: all

 [WARNING]: provided hosts list is empty, only localhost is available

PLAY [localhost] ********************************************************************************************************************************************

TASK [Gathering Facts] **************************************************************************************************************************************
Wednesday 04 July 2018  09:07:48 +0000 (0:00:00.152)       0:00:00.152 ********
ok: [localhost]

TASK [gen hosts if 'local' env is used] *********************************************************************************************************************
Wednesday 04 July 2018  09:07:57 +0000 (0:00:08.687)       0:00:08.839 ********
fatal: [localhost -> localhost]: FAILED! => {"changed": false, "checksum": "860c46c0e7166eccc3f8bebf1070b2a5ca001210", "failed": true, "msg": "Destination /openwhisk/ansible/environments/local not writable"}

Destination /openwhisk/ansible/environments/local not writable

PLAY RECAP **************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=1

Wednesday 04 July 2018  09:07:58 +0000 (0:00:01.137)       0:00:09.977 ********
===============================================================================
Gathering Facts -------------------------------------------------------------------------------------------------------------------------------------- 8.69s
gen hosts if 'local' env is used --------------------------------------------------------------------------------------------------------------------- 1.14s
make: *** [init-couchdb] Error 2

Solved it by giving permissions to ansible folder in the make file

Solved it by giving permissions to ansible folder in the make file

I have the same problem. Can you please guide me?


Write out CycloneDX 1.3 by default

Please have a look at the individual commit messages for the details.

Merging despite the unrelated Conan test failures.


Add fast deploy on other platforms

I just discovered Ackee Analytics and I like it a lot, visuals, mission, and specially the privacy it gives in comparison to google, I'm a frontend developer, student, it's my first time dealing with backend, tried the installation guides and failed miserably. :sweat_smile:
I think it would be a nice enhacement to be able to fast deploy Ackee on other services for folks like me. There aren't many simple free alternatives to host Ackee besides heroku (the button don't work anymore at this date 01/09/2020), the mongodb addon needs credit card and it seems that it will be discontinued in November 10, 2020...
Here are some FREE with limits services that I think (correct me if I'm wrong) it can run Ackee:
Okteto
They have a fast deploy button, it's a kubernetes platform, also support helm charts and a lot of databases, including mongo, maria, postgre and others. It sleeps in 24 hours after no activity.

https://okteto.com/docs/cloud/develop-on-okteto-button
Fly.io
Dockers images, but they have their own commands, we get $10 every month to use on their services, seems like they deploy the apps in multiple servers, basically a CDN, they have something called turboku, a way to connect heroku apps, more info here: https://fly.io/heroku
Alwaysdata
Regular hosting with 100 MB of space, they have nodeJS, yarn, mongodb and others, I guess we can run Ackee but the space is too little, I assume... But I think we can use Atlas just for the database. (I couldn't figure out how to do the connection too. :disappointed:)
Qovery
They have a free tier for developers, community projects and small stuff, I don't think it sleeps or anything like this but it's full CLI, the docs teach how to deploy with Git and Docker, also support databases like MongoDB, Postgre, etc. Seems like a good place for hosting Ackee, if anyone make it work, please comment.
Kintohub
Making Ackee work on Kintohub is easy (even for me. 😅), supports linking to git and even regular https for public and private repos, dockers, databases, it seems perfect but... Ackee doesn't seem to deploy with 256mb of memory, that's the free plan offer, if you upgrade to the pay-as-you-go (needs credit/debit card) you get $10 every month for free to use on their services, but you will get billed if you use more than $10, the credit card unlinking is also hard (I'm still trying and no response to this date yet). So, if you can control your expenses and maintain under $10, it's free.
I would volunter myself to make the guides, but I just don't know how to setup everything. Any help is appreciated, also tell me what you think or if you use other (preferebly free) services.

Sounds like a good idea to add more free services to the documentation. Help is welcome! Feel free to suggest more hosting options.

Related: https://github.com/electerious/Ackee/issues/60

@electerious @Go-Merk thank you for this project and this contribution. I really want to start using Ackee but I'm not seeing what would be the best host for this. I was thinking of using Vultr (5€) as I have other services there, but I was wondering if there's a cheaper service available for deploy Ackee.

Netlify + MongoDB Atlas might be a good solution. Ackee will also support Vercel in the future which might a good choice, too. I however don't have enough data to say that the free plans are enough long-term.

Netlify + MongoDB Atlas might be a good solution. Ackee will also support Vercel in the future which might a good choice, too. I however don't have enough data to say that the free plans are enough long-term.

Thank you for the fast reply! Yes, I saw the pull request for Vercel. I already use Vercel so I'm excited to use it together with MongoDB Atlas 😁

Would be great to know to deploy on Linode, just spend some hours trying to, but kept winding up with errors that I'm not sure what to make of. This is part of the error, seems to be timing out in 10 seconds.
{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"MongooseServerSelectionError: connection timed out","trace":["Runtime.UnhandledPromiseRejection: MongooseServerSelectionError: connection timed out","    at process. (/var/runtime/index.js:35:15)","    at process.emit (events.js:314:20)","    at processPromiseRejections (internal/process/promises.js:209:33)","    at processTicksAndRejections (internal/process/task_queues.js:98:32)"]}
I used the deploy with Netlify option, and setup my own MongoDB server with administrative user and Ackee database. Tested connecting to it from another Linode but when it comes to Ackee, it didn't work with connecting and I'm not sure what I missed. I've tried modifying the connection string with using the mongo login credentials and without (with mongo security disabled).
I'm giving Uberspace a try.

In addition to Uberspace, I would also tip in https://www.cloudron.io/ (free for 2 apps).
Ackee is here : https://www.cloudron.io/store/com.electerious.ackee.html and it is fully packaged.

The get started guide keeps growing. I will close this issue as it's not really an issue, but I enabled GitHub discussions in case someone wants to post more hosting suggestions 😊 https://github.com/electerious/Ackee/discussions


ROS connects but java runtime exception occurs

I also posted this at
https://answers.ros.org/question/279027/tango-ros-streamer-fail/
I installed tango_ros_streamer from the play store, following the instructions here: http://wiki.ros.org/tango_ros_streamer
The app loaded and connected to the roscore on my main computer and the ROS indicator turned green. However, the tango indicator is yellow and I am not seeing any data other than in the /android/IMU topic, which is publishing normally.  The log indicates a Java runtime exception after "ROS CONNECTION latch released!"
Here are the topics that exist:
/android/imu
/rosout
/rosout_agg
/tango/status
Here are the nodes that exist:
/android
/parameter_node
/rosout
/tango_service_client_node
Here is the tango log file (<IP_ADDRESS> is the correct address for the tango):

ed: Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</parameter_node,
http://<IP_ADDRESS>:33283/>,
TopicIdentifier>,
Topic<TopicIdentifier,
TopicDescription<rosgraph_msgs/Log,
acffd30cd6b6de30f120938c17c593fb>>>>
I/Registrar( 4394): Response<Success,
Success, []> I/Registrar( 4394):
Response<Success, Success, []>
I/DefaultPublisher( 4394): Publisher
registered:
Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</tango_service_client_node,
http://<IP_ADDRESS>:38113/>,
TopicIdentifier>,
Topic<TopicIdentifier,
TopicDescription<rosgraph_msgs/Log,
acffd30cd6b6de30f120938c17c593fb>>>>
I/DefaultPublisher( 4394): Publisher
registered:
Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</android,
http://<IP_ADDRESS>:56484/>,
TopicIdentifier>,
Topic<TopicIdentifier,
TopicDescription<rosgraph_msgs/Log,
acffd30cd6b6de30f120938c17c593fb>>>>
I/Registrar( 4394): Registering
subscriber:
Subscriber<Topic<TopicIdentifier</tango/status>,
TopicDescription<std_msgs/Int8,
27ffa0c9c4b8fb8492252bcad9e5c57b>>>
I/Registrar( 4394): Registering
publisher:
Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</android,
http://<IP_ADDRESS>:56484/>,
TopicIdentifier</android/imu>>,
Topic<TopicIdentifier</android/imu>,
TopicDescription<sensor_msgs/Imu,
6a62c6daae103f4ff57a132d6f95cec2>>>>
I/Registrar( 4394): Response<Success,
Success, []> I/Registrar( 4394):
Response<Success, Success, []>
I/DefaultPublisher( 4394): Publisher
registered:
Publisher<PublisherDefinition<PublisherIdentifier<NodeIdentifier</android,
http://<IP_ADDRESS>:56484/>,
TopicIdentifier</android/imu>>,
Topic<TopicIdentifier</android/imu>,
TopicDescription<sensor_msgs/Imu,
6a62c6daae103f4ff57a132d6f95cec2>>>>
I/RunningActivity( 5105):
initAndStartRosJavaNode
I/RunningActivity( 5105): Waiting for
ROS CONNECTION latch release...
I/RunningActivity( 5105): ROS
CONNECTION latch released!

That release almost works.  It comes up with both the ROS and Tango lights green, but then the Tango light turns red.
The log says:
Successfully connected to Tango
Then the next two lines are:
tango_ros_node:388 Error, could not get a first valid Pose
tango_ros_util.cpp:62 Could not connect to the Tnago service.

@dan9thsense I tested the old release pointed by @jubeira on a Tango Development device and it works fine.
Can you try again and be sure to point the camera of the device to a "feature rich environment" (e.g. pointing at your surroundings, not lying on a table). That could be an issue, since the app needs a first valid pose.
Also, in this version of the app, to receive data on topics, you should enable each type of data you want from the navigation drawer (press the menu icon on the right corner).

Thanks for investigating this.  I will try that on Monday, as I am traveling this week.  The camera was just pointing at a wall, so perhaps that is the issue.

Good news!  That fixed it-- data and images are coming through.
Thanks for your time and persistence to address this issue.  You have resurrected my Tango device and, for the first time, it will be a useful device.

Good news! That fixed it-- data and images are coming through.
Thanks for your time and persistence to address this issue. You have resurrected my Tango device and, for the first time, it will be a useful device.

Hello, thanks for the above info - I have got my hands on a spare Tango development device (Yellowstone tablet, same android/kernel/tango-core version as dan9thsense's), and with the help of this thread I have been able to get it publishing to ROS. Thanks!
Worth noting - I have tried some more recent releases of the streamer app, and found that all versions work from 1.0-15 up to and including 1.3.0.  It looks like it was the 1.3.1 changes which broke the app for the yellowstone tablet.
This makes sense, as the release notes mention changes for supporting tango core m20, while the last tango core release that supported the yellowstone tablet was Hopak.
So I'd recommend future people trying to run tango_ros_streamer on a yellowstone tablet stick to release 1.3.0 (https://github.com/Intermodalics/tango_ros/releases/tag/v1.3.0)


.NET 5 support: Breaking changes

This issue tracks changes that will need to be made when this project changes to run on .NET 5:

https://github.com/aspnet/Announcements/issues/438: Fields on RenderTreeFrame have become properties #438

can mobileblazor bindings app consume library based on net5.0? is this planned for .NET5.0 release timeframe or later.

We're discussing this with .NET folks. It's definitely in the plans to support the latest .NET5 stuff but it's not yet ready. I think it is currently blocked on some Xamarin.Forms support that is being looked at.

See https://github.com/xamarin/Xamarin.Forms/issues/12112 for this.


Indentation: Weird indentation in this case

I have the default settings and a file like this with 6 leading spaces:
      "foo": "bar"

The status bar indicates to me that pressing tab will insert 1 tab, but when I press tab on the next line, I get mixed tab/whitespaces:

Refs: https://github.com/Microsoft/vscode/issues/3922

This is by design. Pressing Tab on an empty line is implemented "smart". We do not have a setting to turn this off.
It brings indentation to the previous indented line or if the previous indented line ends with {, it brings indentation to the previous indented line + 1 indent, etc.

In this case specifically, the previous indent was 6 spaces. The indent picks up that it should add 6 spaces, but since it is configured with tabs, it turns as many of those into tabs as possible, hence the 1 tab + 2 spaces.

It has to do mixed whitespace because of the JSDoc case, e.g.:

Where pressing Enter inserts 1 tab and 1 space. Then the language regex rules kick in and append a *

@bpasero I could make it so that pressing tab never inserts mixed whitespace, but as shown above, this might break other use-cases (such as JSDoc) where mixed whitespace is desired.
So if you have any ideas...

i am not a strong enough user of this feature, lets see what community says


Sqlproj schema compare against project doesn't refresh the model after changes are applied

Azure Data Studio Version:
OS Version:

Steps to Reproduce:

Create a project from a db with tables
Add a table to sql proj
Open schema compare and select db as source and project as target
compare and apply changes to delete the table
build the project and make sure table is deleted
in same schema compare window click on compare again
7
Expected: should show no difference
Actual: got an error for the missing script:
Schema Compare failed: Unexpected exception caught during population of target model: Could not find file 'c:\Users[user]\SqlProjTest\DatabaseProjectkeep_AdventureWorks2019\Tables\Table1.sql'.

Does this issue occur when all extensions are disabled?: Yes/No

Reopening the Schema Compare window works; ideally would refresh the model schema compare uses

I'm not able to repro this anymore. Might have been fixed with https://github.com/microsoft/azuredatastudio/pull/18890, since that reloads the projects


Java 11.1: Variable Length Arguments

Description
Add audio, documentation, and video regarding the Variable Length Arguments.

Location of File to be added
The files should be added inside the Variable Length Arguments  folder which is inside the Varargs  folder present in the   Java  main folder.  The documentation file can be in the .md/.py/.ipynb format. Audio should be in .mp3 format and to be submitted through a Google drive link. Video can be in any format and should be submitted through a Google Drive link.
Note:

You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time.
Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns.
You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned.
Issues will be assigned on a first come first serve basis.

Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

\assign Document

/assign document

@shreya40 You have been assigned documentation.

/assign

/assign Document


Virtual Service with host containing IP address doesn’t work

Bug description
My use case is to access external http endpoint through egress gateway. For that, I create a service entry and a virtual service to have host set as IP of the external endpoint. After application of the virtual service, all the proxies go to STALE state. And I see following logs for istio-proxy:
warning	envoy config	[external/envoy/source/common/config/grpc_subscription_impl.cc:101] gRPC config for type.googleapis.com/envoy.api.v2.RouteConfiguration rejected: Only unique values for domains are permitted. Duplicate entry of domain <IP>
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
All the proxies should have correct route to the external IP and proxy states should be OK not STALE. But I see in the sidecar of source pod does not point to egress gateway cluster for this endpoint's route
Steps to reproduce the bug

Create service entry for the external IP with http protocol with address and endpoint set as the IP address
Apply the service entry created above
Create a virtual service with the IP as the host (so that it is used whenever user hits the IP from within the cluster)
Apply the virtual service created above
See output of command  istioctl proxy-status, it will give all proxy status as stale
Check logs for istio-proxy for any pod, it will give gRPC error mentioned in bug description

Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote
client version: 1.6.8
control plane version: 1.6.8
kubectl version
Major:"1", Minor:"18"
Major:"1", Minor:"18"
How was Istio installed?
Using istioctl install
Please let me know if we can use IP address as host in virtual service as mentioned here because this seem to trigger when I use IP in host in virtual service.

can you add the config you used so we can reproduce?
cc @ramaraochavali

Sure, please find configurations for gateway, service entry and virtual service below:
Egress gateway:
`apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
name: istio-egressgateway
spec:
selector:
istio: egressgateway
servers:

port:
number: 80
name: http
protocol: HTTP
hosts:

"*"`

Service Entry:
`
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
name: ip-external
spec:
hosts:

"ip-external.com"
addresses:
<IP_ADDRESS>
ports:
number: 80
name: http
protocol: HTTP
resolution: STATIC
endpoints:
address: <IP_ADDRESS>
`

Virtual Service:
`
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: external-ip-virtual-service
spec:
hosts:

<IP_ADDRESS>
gateways:
istio-egressgateway
mesh
http:
match:

gateways:

mesh
port: 80
route: # route requests from mesh to egress gateway

destination:
host: istio-egressgateway.istio-system.svc.cluster.local
port:
number: 80

match:

gateways:

istio-egressgateway
port: 80
route: # route requests from egress gateway to external service

destination:
host: ip-external.com
port:
number: 80
`

Then try istioctl proxy-status you'll see STALE state for RDS for all sidecars where this is applied.
Additionally, check logs of istio-proxy container in any of the pods with sidecar
Let me know if any other information is required.

I have confirmed this is fixed by #24455 in 1.7+ Thanks for the info!

@howardjohn The issue still exists it seems in 1.9. With IP has host I'm unable to route traffic via egress gateway. Could you please help with an example if possible?

Below is the configuration I'm using :
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: "bulksms-ext"
spec:
  hosts:
  - bulksms.ext
  addresses:
  - IP_ADDRESS/32
  ports:
  - number: 8080
    name: http-8080
    protocol: HTTP
  resolution: STATIC
  endpoints:
  - address: IP_ADDRESS
  location: MESH_EXTERNAL

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: direct-sms-email-via-egress-gw-{{ .Values.env }}
spec:
  hosts:
  - IP_ADDRESS
  gateways:
  - my-egress-gateway
  - mesh
  http:
  - match:
    - gateways:
      - mesh
      port: 8080
    route:
    - destination:
        host: istio-egressgateway.istio-system.svc.cluster.local
        port:
          number: 80
  - match:
    - gateways:
      - my-egress-gateway
      port: 80
    route:
    - destination:
        host: bulksms.ext
        port:
          number: 8080

The response I'm getting on sending a request:
Trying IP_ADDRESS:8080...
* Connected to IP_ADDRESS (IP_ADDRESS) port 8080 (#0)
> GET / HTTP/1.1
> Host: IP_ADDRESS:8080
> User-Agent: curl/7.75.0-DEV
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 503 Service Unavailable
< content-length: 84
< content-type: text/plain
< date: Thu, 11 Mar 2021 13:58:09 GMT
< server: envoy
<
* Connection #0 to host IP_ADDRESS left intact
upstream connect error or disconnect/reset before headers. reset reason: local reset