Demo bug report with all fields filled and long debug output pasted directly

Steps to reproduce

What actions do you take?
Have you set any run-time or compile-time configuration options?
More steps…

Start Bitcoin Core and try to make a transaction with bitcoin-cli.
No special options
Outcome
What did you expect?
It should send a transaction
What happened instead?
It crashed
Relevant log output
2022-12-01T11:44:31Z Bitcoin Core version v24.99.0-e334f7a54592 (debug build)
2022-12-01T11:44:31Z Signet derived magic (message start): 0a03cf40
2022-12-01T11:44:31Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2022-12-01T11:44:31Z Using RdSeed as an additional entropy source
2022-12-01T11:44:31Z Using RdRand as an additional entropy source
2022-12-01T11:44:31Z Default data directory /home/will/.bitcoin
2022-12-01T11:44:31Z Using data directory /home/will/.bitcoin/signet
2022-12-01T11:44:31Z Config file: /home/will/.bitcoin/bitcoin.conf
2022-12-01T11:44:31Z Config file arg: daemon="1"
2022-12-01T11:44:31Z Config file arg: discover="1"
2022-12-01T11:44:31Z Config file arg: listen="1"
2022-12-01T11:44:31Z Config file arg: server="1"
2022-12-01T11:44:31Z Config file arg: [regtest] rpcpassword=****
2022-12-01T11:44:31Z Config file arg: [regtest] rpcport="18443"
2022-12-01T11:44:31Z Config file arg: [regtest] rpcuser=****
2022-12-01T11:44:31Z Config file arg: [signet] blocksdir="/media/will/crucial1/.bitcoin"
2022-12-01T11:44:31Z Config file arg: [signet] daemon="1"
2022-12-01T11:44:31Z Config file arg: [signet] debug="1"
2022-12-01T11:44:31Z Config file arg: [signet] listen="1"
2022-12-01T11:44:31Z Config file arg: [signet] rpcpassword=****
2022-12-01T11:44:31Z Config file arg: [signet] rpcuser=****
2022-12-01T11:44:31Z Config file arg: [signet] server="1"
2022-12-01T11:44:31Z Config file arg: [signet] wallet="/home/will/.bitcoin/signet/wallets/test-descriptor"
2022-12-01T11:44:31Z Config file arg: [test] blocksdir="/media/will/crucial1/.testnet"
2022-12-01T11:44:31Z Config file arg: [test] dbcache="16384"
2022-12-01T11:44:31Z Config file arg: [test] rpcpassword=****
2022-12-01T11:44:31Z Config file arg: [test] rpcuser=****
2022-12-01T11:44:31Z Command-line arg: signet=""
2022-12-01T11:44:31Z Using at most 125 automatic connections (1024 file descriptors available)
2022-12-01T11:44:31Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2022-12-01T11:44:31Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2022-12-01T11:44:31Z Script verification uses 15 additional threads
2022-12-01T11:44:31Z [lock] Enter: lock contention m_mutex, ./checkqueue.h:78 started
2022-12-01T11:44:31Z [lock] Enter: lock contention m_mutex, ./checkqueue.h:78 completed (1μs)
2022-12-01T11:44:31Z [lock] Enter: lock contention m_mutex, ./checkqueue.h:78 started
2022-12-01T11:44:31Z [lock] Enter: lock contention m_mutex, ./checkqueue.h:78 completed (1μs)
2022-12-01T11:44:31Z scheduler thread start
2022-12-01T11:44:31Z [http] Allowing HTTP connections from: <IP_ADDRESS>/8 ::1/128
2022-12-01T11:44:31Z [libevent:debug] event_add: event: 0x564edf81b680 (fd 10), EV_READ    call 0x7f58cc179620
2022-12-01T11:44:31Z [libevent:debug] Epoll ADD(1) on fd 10 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z Binding RPC on address ::1 port 38332
2022-12-01T11:44:31Z [libevent:debug] event_add: event: 0x564edf81c1e8 (fd 11), EV_READ    call 0x7f58cc17eb70
2022-12-01T11:44:31Z [libevent:debug] Epoll ADD(1) on fd 11 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z [libevent:debug] Bound to port 38332 - Awaiting connections ...
2022-12-01T11:44:31Z Binding RPC on address <IP_ADDRESS> port 38332
2022-12-01T11:44:31Z [libevent:debug] event_add: event: 0x564edf81c968 (fd 12), EV_READ    call 0x7f58cc17eb70
2022-12-01T11:44:31Z [libevent:debug] Epoll ADD(1) on fd 12 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z [libevent:debug] Bound to port 38332 - Awaiting connections ...
2022-12-01T11:44:31Z [http] Initialized HTTP server
2022-12-01T11:44:31Z [http] creating work queue of depth 16
2022-12-01T11:44:31Z [rpc] Starting RPC
2022-12-01T11:44:31Z [rpc] Starting HTTP RPC server
2022-12-01T11:44:31Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2022-12-01T11:44:31Z [http] Registering HTTP handler for / (exactmatch 1)
2022-12-01T11:44:31Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2022-12-01T11:44:31Z [http] Starting HTTP server
2022-12-01T11:44:31Z [http] starting 4 worker threads
2022-12-01T11:44:31Z [http] Entering http event loop
2022-12-01T11:44:31Z Using wallet directory /home/will/.bitcoin/signet/wallets
2022-12-01T11:44:31Z init message: Verifying wallet(s)…
2022-12-01T11:44:31Z Using SQLite Version 3.37.2
2022-12-01T11:44:31Z Using wallet /home/will/.bitcoin/signet/wallets/test-descriptor
2022-12-01T11:44:31Z Using /16 prefix for IP bucketing
2022-12-01T11:44:31Z init message: Loading P2P addresses…
2022-12-01T11:44:31Z Error: Invalid or corrupt peers.dat (Invalid network magic number). If you believe this is a bug, please report it to https://github.com/bitcoin/bitcoin/issues. As a workaround, you can move the file ("/home/will/.bitcoin/signet/peers.dat") out of the way (rename, move, or delete) to have a new one created on the next start.
2022-12-01T11:44:31Z [http] Interrupting HTTP server
2022-12-01T11:44:31Z [rpc] Interrupting HTTP RPC server
2022-12-01T11:44:31Z [rpc] Interrupting RPC
2022-12-01T11:44:31Z Shutdown: In progress...
2022-12-01T11:44:31Z [rpc] Stopping HTTP RPC server
2022-12-01T11:44:31Z [http] Unregistering HTTP handler for / (exactmatch 1)
2022-12-01T11:44:31Z [http] Unregistering HTTP handler for /wallet/ (exactmatch 0)
2022-12-01T11:44:31Z [rpc] Stopping RPC
2022-12-01T11:44:31Z [rpc] RPC stopped.
2022-12-01T11:44:31Z [http] Stopping HTTP server
2022-12-01T11:44:31Z [http] Waiting for HTTP worker threads to exit
2022-12-01T11:44:31Z [libevent:debug] event_del: 0x564edf81c1e8 (fd 11), callback 0x7f58cc17eb70
2022-12-01T11:44:31Z [libevent:debug] Epoll DEL(1) on fd 11 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:44:31Z [libevent:debug] event_active: 0x564edf81b680 (fd 10), res 2, callback 0x7f58cc179620
2022-12-01T11:44:31Z [libevent:debug] event_process_active: event: 0x564edf81b680, EV_READ   call 0x7f58cc179620
2022-12-01T11:44:31Z [libevent:debug] event_del: 0x564edf81c968 (fd 12), callback 0x7f58cc17eb70
2022-12-01T11:44:31Z [libevent:debug] Epoll DEL(1) on fd 12 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:44:31Z [libevent:debug] event_active: 0x564edf81b680 (fd 10), res 2, callback 0x7f58cc179620
2022-12-01T11:44:31Z [libevent:debug] event_process_active: event: 0x564edf81b680, EV_READ   call 0x7f58cc179620
2022-12-01T11:44:31Z [http] Waiting for HTTP event thread to exit
2022-12-01T11:44:31Z [libevent:debug] event_base_loop: no events registered.
2022-12-01T11:44:31Z [http] Exited http event loop
2022-12-01T11:44:31Z [libevent:debug] event_del: 0x564edf81b680 (fd 10), callback 0x7f58cc179620
2022-12-01T11:44:31Z [libevent:debug] Epoll DEL(1) on fd 10 okay. Old events were 2; read change was 2 (del); write change was 0 (none); close change was 0 (none)
2022-12-01T11:44:31Z [libevent:debug] event_base_free_: 0 events freed
2022-12-01T11:44:31Z [http] Stopped HTTP server
2022-12-01T11:44:31Z scheduler thread exit
2022-12-01T11:44:31Z Shutdown: done

2022-12-01T11:51:42Z Bitcoin Core version v24.99.0rc4-51151cc4f1bc (debug build)
2022-12-01T11:51:42Z Signet derived magic (message start): 0a03cf40
2022-12-01T11:51:42Z Using the 'x86_shani(1way,2way)' SHA256 implementation
2022-12-01T11:51:42Z Using RdSeed as an additional entropy source
2022-12-01T11:51:42Z Using RdRand as an additional entropy source
2022-12-01T11:51:42Z Default data directory /home/will/.bitcoin
2022-12-01T11:51:42Z Using data directory /home/will/.bitcoin/signet
2022-12-01T11:51:42Z Config file: /home/will/.bitcoin/bitcoin.conf
2022-12-01T11:51:42Z Config file arg: daemon="1"
2022-12-01T11:51:42Z Config file arg: discover="1"
2022-12-01T11:51:42Z Config file arg: listen="1"
2022-12-01T11:51:42Z Config file arg: server="1"

2022-12-01T11:51:42Z Config file arg: [regtest] rpcpassword=****
2022-12-01T11:51:42Z Config file arg: [regtest] rpcport="18443"
2022-12-01T11:51:42Z Config file arg: [regtest] rpcuser=****
2022-12-01T11:51:42Z Config file arg: [signet] blocksdir="/media/will/crucial1/.bitcoin"
2022-12-01T11:51:42Z Config file arg: [signet] daemon="1"
2022-12-01T11:51:42Z Config file arg: [signet] debug="1"
2022-12-01T11:51:42Z Config file arg: [signet] listen="1"
2022-12-01T11:51:42Z Config file arg: [signet] rpcpassword=****
2022-12-01T11:51:42Z Config file arg: [signet] rpcuser=****
2022-12-01T11:51:42Z Config file arg: [signet] server="1"
2022-12-01T11:51:42Z Config file arg: [signet] wallet="/home/will/.bitcoin/signet/wallets/test-descriptor"
2022-12-01T11:51:42Z Config file arg: [test] blocksdir="/media/will/crucial1/.testnet"
2022-12-01T11:51:42Z Config file arg: [test] dbcache="16384"
2022-12-01T11:51:42Z Config file arg: [test] rpcpassword=****
2022-12-01T11:51:42Z Config file arg: [test] rpcuser=****
2022-12-01T11:51:42Z Command-line arg: signet=""
2022-12-01T11:51:42Z Using at most 125 automatic connections (1024 file descriptors available)
2022-12-01T11:51:42Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2022-12-01T11:51:42Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2022-12-01T11:51:42Z Script verification uses 15 additional threads
2022-12-01T11:51:42Z scheduler thread start
2022-12-01T11:51:42Z [http] Allowing HTTP connections from: <IP_ADDRESS>/8 ::1/128
2022-12-01T11:51:42Z [libevent:debug] event_add: event: 0x557bfefd9cc0 (fd 10), EV_READ    call 0x7fb7a66a6620
2022-12-01T11:51:42Z [libevent:debug] Epoll ADD(1) on fd 10 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:51:42Z [http] Binding RPC on address ::1 port 38332
2022-12-01T11:51:42Z [libevent:debug] event_add: event: 0x557bfefda3c8 (fd 11), EV_READ    call 0x7fb7a66abb70
2022-12-01T11:51:42Z [libevent:debug] Epoll ADD(1) on fd 11 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:51:42Z [libevent:debug] Bound to port 38332 - Awaiting connections ...
2022-12-01T11:51:42Z [http] Binding RPC on address <IP_ADDRESS> port 38332
2022-12-01T11:51:42Z [libevent:debug] event_add: event: 0x557bfefda4c8 (fd 12), EV_READ    call 0x7fb7a66abb70
2022-12-01T11:51:42Z [libevent:debug] Epoll ADD(1) on fd 12 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:51:42Z [libevent:debug] Bound to port 38332 - Awaiting connections ...
2022-12-01T11:51:42Z [http] Initialized HTTP server
2022-12-01T11:51:42Z [http] creating work queue of depth 16
2022-12-01T11:51:42Z [rpc] Starting RPC
2022-12-01T11:51:42Z [rpc] Starting HTTP RPC server
2022-12-01T11:51:42Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2022-12-01T11:51:42Z [http] Registering HTTP handler for / (exactmatch 1)
2022-12-01T11:51:42Z [http] Registering HTTP handler for /wallet/ (exactmatch 0)
2022-12-01T11:51:42Z [http] Starting HTTP server
2022-12-01T11:51:42Z [http] starting 4 worker threads
2022-12-01T11:51:42Z [http] Entering http event loop
2022-12-01T11:51:42Z Using wallet directory /home/will/.bitcoin/signet/wallets
2022-12-01T11:51:42Z init message: Verifying wallet(s)…
2022-12-01T11:51:42Z Using SQLite Version 3.37.2
2022-12-01T11:51:42Z Using wallet /home/will/.bitcoin/signet/wallets/test-descriptor
2022-12-01T11:51:42Z Using /16 prefix for IP bucketing
2022-12-01T11:51:42Z init message: Loading P2P addresses…
2022-12-01T11:51:42Z Creating peers.dat because the file was not found ("/home/will/.bitcoin/signet/peers.dat")
2022-12-01T11:51:42Z init message: Loading banlist…
2022-12-01T11:51:42Z [net] Loaded 0 banned node addresses/subnets  0ms
2022-12-01T11:51:42Z [net] setting try another outbound peer=false
2022-12-01T11:51:42Z SetNetworkActive: true
2022-12-01T11:51:42Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 48 blocks
2022-12-01T11:51:42Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 12 blocks
2022-12-01T11:51:42Z [estimatefee] Reading estimates: 190 buckets counting confirms up to 1008 blocks
2022-12-01T11:51:42Z Cache configuration:
2022-12-01T11:51:42Z * Using 2.0 MiB for block index database
2022-12-01T11:51:42Z * Using 8.0 MiB for chain state database
2022-12-01T11:51:42Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2022-12-01T11:51:42Z init message: Loading block index…
2022-12-01T11:51:42Z Assuming ancestors of block 000000d1a0e224fa4679d2fb2187ba55431c284fa1b74cbc8cfda866fd4d2c09 have valid signatures.
2022-12-01T11:51:42Z Setting nMinimumChainWork=000000000000000000000000000000000000000000000000000001291fc22898
2022-12-01T11:51:42Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2022-12-01T11:51:42Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2022-12-01T11:51:42Z Opening LevelDB in /home/will/.bitcoin/signet/blocks/index
2022-12-01T11:51:42Z [leveldb:debug] Recovering log #107
2022-12-01T11:51:42Z [leveldb:debug] Level-0 table #109: started
2022-12-01T11:51:42Z [leveldb:debug] Level-0 table #109: 12272 bytes OK
2022-12-01T11:51:42Z [leveldb:debug] Delete type=3 #105
2022-12-01T11:51:42Z [leveldb:debug] Delete type=0 #107
2022-12-01T11:51:42Z Opened LevelDB successfully
2022-12-01T11:51:42Z [leveldb:debug] Compacting 4@0 + 1@1 files
2022-12-01T11:51:42Z Using obfuscation key for /home/will/.bitcoin/signet/blocks/index:<PHONE_NUMBER>000000
2022-12-01T11:51:42Z [leveldb:debug] Generated table #111@0: 4229 keys, 605490 bytes
2022-12-01T11:51:42Z [leveldb:debug] Compacted 4@0 + 1@1 files => 605490 bytes
2022-12-01T11:51:42Z [leveldb:debug] compacted to: files[ 0 1 1 0 0 0 0 ]
2022-12-01T11:51:44Z LoadBlockIndexDB: last block file = 4
2022-12-01T11:51:44Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=10160, size=57729075, heights=108171...119313, time=2022-09-15...2022-12-01)
2022-12-01T11:51:44Z Checking all blk files are present...
2022-12-01T11:51:45Z [leveldb] LevelDB using max_open_files=1000 (default=1000)
2022-12-01T11:51:45Z Opening LevelDB in /home/will/.bitcoin/signet/chainstate
2022-12-01T11:51:45Z [leveldb:debug] Recovering log #760
2022-12-01T11:51:45Z [leveldb:debug] Level-0 table #772: started
2022-12-01T11:51:45Z [leveldb:debug] Level-0 table #772: 47992 bytes OK
2022-12-01T11:51:45Z [leveldb:debug] Delete type=3 #759
2022-12-01T11:51:45Z [leveldb:debug] Delete type=0 #760
2022-12-01T11:51:45Z Opened LevelDB successfully
2022-12-01T11:51:45Z Using obfuscation key for /home/will/.bitcoin/signet/chainstate: 9e297a4f20fd3ecb
2022-12-01T11:51:45Z Loaded best chain: hashBestChain=00000072d3d0525ef68027c9c844ae7e869056a4fae696158dec994bf78e2181 height=119313 date=2022-12-01T11:30:29Z progress=0.999986
2022-12-01T11:51:45Z init message: Verifying blocks…
2022-12-01T11:51:45Z Verifying last 6 blocks at level 3
2022-12-01T11:51:45Z [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2022-12-01T11:51:45Z No coin database inconsistencies in last 6 blocks (8 transactions)
2022-12-01T11:51:45Z  block index            2222ms
2022-12-01T11:51:45Z Using SQLite Version 3.37.2
2022-12-01T11:51:45Z Using wallet /home/will/.bitcoin/signet/wallets/test-descriptor
2022-12-01T11:51:45Z init message: Loading wallet…
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Wallet file version = 10500, last client version = 249900
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = adf1d406aa4a741e75b4d7c75092da40c95cc184b853ead478dfd02098482057, type = legacy, internal = false
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = cf07b58d1c8ac3893aba1abb0dc05feef3a9169318024ad54c9ee90fd2921280, type = p2sh-segwit, internal = false
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = 2295b7686d6a29432cbb03f31ca5bdcd23e22f646768e6ceabd258106878175f, type = bech32, internal = false
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = e1d90c7371f32533ff2db1847ccbc2d9bc4f7e6ee64f7e1a3771a60e92d95964, type = bech32m, internal = false
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = 2ab8410b58639f9ae00c3e590ee82b9236c872f6a1e66a7803a05e7283a99fd1, type = legacy, internal = true
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = ded6ad73ececbd006d09ef15319bab30187f1e4828b330324584d18b63e3b15d, type = p2sh-segwit, internal = true
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = b51440a0c755c032f1a1b20fbe9efbb373bf58e64641211949f286107ae5b160, type = bech32, internal = true
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Setting spkMan to active: id = 25b79b2e95a1efcca1ba56bbe82f7187b2ad777739baa445f37ddda01b916b2c, type = bech32m, internal = true
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Keys: 8 plaintext, 0 encrypted, 0 w/ metadata, 8 total. Unknown wallet records: 0
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] Wallet completed loading in             545ms
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] setKeyPool.size() = 8000
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] mapWallet.size() = 4
2022-12-01T11:51:45Z [/home/will/.bitcoin/signet/wallets/test-descriptor] m_address_book.size() = 5
2022-12-01T11:51:45Z Setting NODE_NETWORK on non-prune mode
2022-12-01T11:51:45Z block tree size = 119314
2022-12-01T11:51:45Z nBestHeight = 119313
2022-12-01T11:51:45Z loadblk thread start
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 started
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 completed (4μs)
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 started
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x557c00c55df0 (fd 24), EV_READ    call 0x7fb7a66a6620
2022-12-01T11:51:45Z [libevent:debug] Epoll ADD(1) on fd 24 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 completed (5μs)
2022-12-01T11:51:45Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2022-12-01T11:51:45Z loadblk thread exit
2022-12-01T11:51:45Z torcontrol thread start
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 started
2022-12-01T11:51:45Z [lock] Enter: lock contention cs_args, util/system.cpp:1095 completed (54μs)
2022-12-01T11:51:45Z Bound to <IP_ADDRESS>:38334
2022-12-01T11:51:45Z Bound to [::]:38333
2022-12-01T11:51:45Z Bound to <IP_ADDRESS>:38333
2022-12-01T11:51:45Z Loaded 2 addresses from "anchors.dat"
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb730001940 (fd -1), EV_READ    call 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd -1),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z 2 block-relay-only anchors will be tried for connections.
2022-12-01T11:51:45Z init message: Starting network threads…
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb730001940 (fd -1), callback 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb7300019c0 (fd -1), callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb730001940 (fd 28), EV_READ    call 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] Epoll ADD(1) on fd 28 okay. Old events were 0; read change was 1 (add); write change was 0 (none); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd 28),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(5) on fd 28 okay. Old events were 2; read change was 0 (none); write change was 1 (add); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd 28),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z dnsseed thread start
2022-12-01T11:51:45Z net thread start
2022-12-01T11:51:45Z [tor] Reading cached private key from /home/will/.bitcoin/signet/onion_v3_private_key
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb7300019c0 (fd 28), res 4, callback 0x7fb7a669c500
2022-12-01T11:51:45Z Loading addresses from DNS seed seed.signet.bitcoin.sprovoost.nl.
2022-12-01T11:51:45Z addcon thread start
2022-12-01T11:51:45Z init message: Done loading
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb7300019c0,  EV_WRITE  call 0x7fb7a669c500
2022-12-01T11:51:45Z opencon thread start
2022-12-01T11:51:45Z msghand thread start
2022-12-01T11:51:45Z [tor] Successfully connected!
2022-12-01T11:51:45Z [lock] Enter: lock contention m_mutex, random.cpp:415 started
2022-12-01T11:51:45Z [lock] Enter: lock contention m_mutex, random.cpp:415 completed (5μs)
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb7300019c0 (fd 28), callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(1) on fd 28 okay. Old events were 6; read change was 0 (none); write change was 2 (del); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb730001940 (fd 28), res 2, callback 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb730001940, EV_READ   call 0x7fb7a669bd70
2022-12-01T11:51:45Z [tor] Connected to Tor version <IP_ADDRESS>
2022-12-01T11:51:45Z [tor] Supported authentication method: COOKIE
2022-12-01T11:51:45Z [tor] Supported authentication method: SAFECOOKIE
2022-12-01T11:51:45Z [tor] Using SAFECOOKIE authentication, reading cookie authentication from /run/tor/control.authcookie
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd 28),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(5) on fd 28 okay. Old events were 2; read change was 0 (none); write change was 1 (add); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb7300019c0 (fd 28), res 4, callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb7300019c0,  EV_WRITE  call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb7300019c0 (fd 28), callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(1) on fd 28 okay. Old events were 6; read change was 0 (none); write change was 2 (del); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb730001940 (fd 28), res 2, callback 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb730001940, EV_READ   call 0x7fb7a669bd70
2022-12-01T11:51:45Z [tor] SAFECOOKIE authentication challenge successful
2022-12-01T11:51:45Z [tor] AUTHCHALLENGE ServerHash d5d0a8aec30ad5b88e78c2f39bca4f45d834393424ac8525516bb2ac3200003d ServerNonce ca52758b76a5de6aea6ea27eece9879bfbbb4592cdc523617802568b7bad7351
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd 28),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(5) on fd 28 okay. Old events were 2; read change was 0 (none); write change was 1 (add); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb7300019c0 (fd 28), res 4, callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb7300019c0,  EV_WRITE  call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb7300019c0 (fd 28), callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(1) on fd 28 okay. Old events were 6; read change was 0 (none); write change was 2 (del); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb730001940 (fd 28), res 2, callback 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb730001940, EV_READ   call 0x7fb7a669bd70
2022-12-01T11:51:45Z [tor] Authentication successful
2022-12-01T11:51:45Z [libevent:debug] event_add: event: 0x7fb7300019c0 (fd 28),  EV_WRITE   call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(5) on fd 28 okay. Old events were 2; read change was 0 (none); write change was 1 (add); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb7300019c0 (fd 28), res 4, callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb7300019c0,  EV_WRITE  call 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] event_del: 0x7fb7300019c0 (fd 28), callback 0x7fb7a669c500
2022-12-01T11:51:45Z [libevent:debug] Epoll MOD(1) on fd 28 okay. Old events were 6; read change was 0 (none); write change was 2 (del); close change was 0 (none)
2022-12-01T11:51:45Z [libevent:debug] epoll_dispatch: epoll_wait reports 1
2022-12-01T11:51:45Z [libevent:debug] event_active: 0x7fb730001940 (fd 28), res 2, callback 0x7fb7a669bd70
2022-12-01T11:51:45Z [libevent:debug] event_process_active: event: 0x7fb730001940, EV_READ   call 0x7fb7a669bd70
2022-12-01T11:51:45Z [tor] Get SOCKS port command yielded <IP_ADDRESS>:9050
2022-12-01T11:51:45Z [tor] Configuring onion proxy for <IP_ADDRESS>:9050
2022-12-01T11:51:45Z [tor] ADD_ONION successful
2022-12-01T11:51:45Z [tor] Got service ID am3lpey7n7nqrab66z26hqjepbk536sqxrw3ergndrqsnsoaz5m2jfid, advertising service am3lpey7n7nqrab66z26hqjepbk536sqxrw3ergndrqsnsoaz5m2jfid.onion:38333
2022-12-01T11:51:45Z [tor] Cached service private key to /home/will/.bitcoin/signet/onion_v3_private_key
2022-12-01T11:51:45Z AddLocal(am3lpey7n7nqrab66z26hqjepbk536sqxrw3ergndrqsnsoaz5m2jfid.onion:38333,4)
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[292][20]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[777][32]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[75][61]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[816][42]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[138][50]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[777][11]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[238][35]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[104][6]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[104][57]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[459][24]
2022-12-01T11:51:46Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[305][8]
2022-12-01T11:51:46Z [addrman] Added [2602:ffc5:20::1:51d2]:38333 mapped to AS0 to new[292][16]
2022-12-01T11:51:46Z [addrman] Added [2604:a880:4:1d0::352:6000]:38333 mapped to AS0 to new[383][0]
2022-12-01T11:51:46Z [addrman] Added [2a01:4f8:c010:b76b::1]:38333 mapped to AS0 to new[909][15]
2022-12-01T11:51:46Z [addrman] Added [2a01:4f9:c011:4b8f::1]:38333 mapped to AS0 to new[383][36]
2022-12-01T11:51:46Z [addrman] Added 15 addresses (of 15) from isyyfqeilwfacqmd.internal: 0 tried, 15 new
2022-12-01T11:51:46Z Loading addresses from DNS seed <IP_ADDRESS>
2022-12-01T11:51:46Z [net] Trying to make an anchor connection to <IP_ADDRESS>:28333
2022-12-01T11:51:46Z [net:debug] trying connection <IP_ADDRESS>:28333 lastseen=189.0hrs
2022-12-01T11:51:46Z Loading addresses from DNS seed v7ajjeirttkbnt32wpy3c6w3emwnfr3fkla7hpxcfokr3ysd3kqtzmqd.onion:38333
2022-12-01T11:51:46Z 15 addresses found from DNS seeds
2022-12-01T11:51:46Z dnsseed thread exit
2022-12-01T11:51:46Z [net] Added connection peer=0
2022-12-01T11:51:46Z [net] sending version (103 bytes) peer=0
2022-12-01T11:51:46Z [net] send version message: version 70016, blocks=119313, txrelay=0, peer=0
2022-12-01T11:51:46Z [net:debug] trying connection <IP_ADDRESS> lastseen=0.0hrs
2022-12-01T11:51:46Z [net] received: version (102 bytes) peer=0
2022-12-01T11:51:46Z [net] sending wtxidrelay (0 bytes) peer=0
2022-12-01T11:51:46Z [net] sending sendaddrv2 (0 bytes) peer=0
2022-12-01T11:51:46Z [net] sending verack (0 bytes) peer=0
2022-12-01T11:51:46Z [net] receive version message: /Satoshi:22.0.0/: version 70016, blocks=119313, us=<IP_ADDRESS>:60150, txrelay=1, peer=0
2022-12-01T11:51:46Z [net] added time data, samples 2, offset +0 (+0 minutes)
2022-12-01T11:51:46Z [net] received: wtxidrelay (0 bytes) peer=0
2022-12-01T11:51:46Z [net] received: sendaddrv2 (0 bytes) peer=0
2022-12-01T11:51:46Z [net] received: verack (0 bytes) peer=0
2022-12-01T11:51:46Z New outbound peer connected: version: 70016, blocks=119313, peer=0 (block-relay-only)
2022-12-01T11:51:46Z [net] sending sendcmpct (9 bytes) peer=0
2022-12-01T11:51:46Z [net] sending ping (8 bytes) peer=0
2022-12-01T11:51:46Z [net] sending getheaders (933 bytes) peer=0
2022-12-01T11:51:46Z [net] initial getheaders (119312) to peer=0 (startheight:119313)
2022-12-01T11:51:46Z [net] received: sendheaders (0 bytes) peer=0
2022-12-01T11:51:46Z [net] received: sendcmpct (9 bytes) peer=0
2022-12-01T11:51:46Z [net] received: sendcmpct (9 bytes) peer=0
2022-12-01T11:51:46Z [net] received: ping (8 bytes) peer=0
2022-12-01T11:51:46Z [net] sending pong (8 bytes) peer=0
2022-12-01T11:51:46Z [net] received: addrv2 (16 bytes) peer=0
2022-12-01T11:51:46Z [net] ignoring addrv2 message from block-relay-only peer=0
2022-12-01T11:51:46Z [net] received: getheaders (933 bytes) peer=0
2022-12-01T11:51:46Z [net] getheaders 119313 to end from peer=0
2022-12-01T11:51:46Z [net] sending headers (82 bytes) peer=0
2022-12-01T11:51:46Z [net] received: feefilter (8 bytes) peer=0
2022-12-01T11:51:46Z [net] received: feefilter of 0.00001000 BTC/kvB from peer=0
2022-12-01T11:51:46Z [net] received: pong (8 bytes) peer=0
2022-12-01T11:51:46Z [net] received: headers (82 bytes) peer=0
2022-12-01T11:51:46Z Leaving InitialBlockDownload (latching to false)
2022-12-01T11:51:46Z [net] sending sendheaders (0 bytes) peer=0
2022-12-01T11:51:46Z [net] Added connection peer=1
2022-12-01T11:51:46Z [net] sending version (103 bytes) peer=1
2022-12-01T11:51:46Z [net] send version message: version 70016, blocks=119313, txrelay=1, peer=1
2022-12-01T11:51:46Z [net] received: version (103 bytes) peer=1
2022-12-01T11:51:46Z [net] sending wtxidrelay (0 bytes) peer=1
2022-12-01T11:51:46Z [net] sending sendaddrv2 (0 bytes) peer=1
2022-12-01T11:51:46Z [net] sending verack (0 bytes) peer=1
2022-12-01T11:51:46Z [net] ProcessMessages: advertising address am3lpey7n7nqrab66z26hqjepbk536sqxrw3ergndrqsnsoaz5m2jfid.onion:38333
2022-12-01T11:51:46Z [net] sending getaddr (0 bytes) peer=1
2022-12-01T11:51:46Z [addrman] Moved <IP_ADDRESS>:38333 mapped to AS0 to tried[155][1]
2022-12-01T11:51:46Z [net] receive version message: /Satoshi:22.99.0/: version 70016, blocks=119313, us=<IP_ADDRESS>:53372, txrelay=1, peer=1
2022-12-01T11:51:46Z [net] added time data, samples 3, offset +0 (+0 minutes)
2022-12-01T11:51:46Z [net] received: wtxidrelay (0 bytes) peer=1
2022-12-01T11:51:46Z [net] received: sendaddrv2 (0 bytes) peer=1
2022-12-01T11:51:46Z [net] received: verack (0 bytes) peer=1
2022-12-01T11:51:46Z New outbound peer connected: version: 70016, blocks=119313, peer=1 (addr-fetch)
2022-12-01T11:51:46Z [net] sending sendcmpct (9 bytes) peer=1
2022-12-01T11:51:46Z [net] sending ping (8 bytes) peer=1
2022-12-01T11:51:46Z [net] Advertising address am3lpey7n7nqrab66z26hqjepbk536sqxrw3ergndrqsnsoaz5m2jfid.onion:38333 to peer=1
2022-12-01T11:51:46Z [net] sending addrv2 (44 bytes) peer=1
2022-12-01T11:51:46Z [net] sending getheaders (933 bytes) peer=1
2022-12-01T11:51:46Z [net] initial getheaders (119312) to peer=1 (startheight:119313)
2022-12-01T11:51:46Z [net] sending feefilter (8 bytes) peer=1
2022-12-01T11:51:47Z [net] Trying to make an anchor connection to <IP_ADDRESS>:38333
2022-12-01T11:51:47Z [net:debug] trying connection <IP_ADDRESS>:38333 lastseen=190.0hrs
2022-12-01T11:51:47Z [net] Added connection peer=2
2022-12-01T11:51:47Z [net] sending version (103 bytes) peer=2
2022-12-01T11:51:47Z [net] send version message: version 70016, blocks=119313, txrelay=0, peer=2
2022-12-01T11:51:47Z [net:debug] trying connection v7ajjeirttkbnt32wpy3c6w3emwnfr3fkla7hpxcfokr3ysd3kqtzmqd.onion:38333 lastseen=0.0hrs
2022-12-01T11:51:47Z [net] SOCKS5 connecting v7ajjeirttkbnt32wpy3c6w3emwnfr3fkla7hpxcfokr3ysd3kqtzmqd.onion
2022-12-01T11:51:47Z [proxy] SOCKS5 sending proxy authentication 0:0
2022-12-01T11:51:47Z [net] received: sendheaders (0 bytes) peer=1
2022-12-01T11:51:47Z [net] received: sendcmpct (9 bytes) peer=1
2022-12-01T11:51:47Z [net] received: sendcmpct (9 bytes) peer=1
2022-12-01T11:51:47Z [net] received: ping (8 bytes) peer=1
2022-12-01T11:51:47Z [net] sending pong (8 bytes) peer=1
2022-12-01T11:51:47Z [net] received: getheaders (933 bytes) peer=1
2022-12-01T11:51:47Z [net] getheaders 119313 to end from peer=1
2022-12-01T11:51:47Z [net] sending headers (82 bytes) peer=1
2022-12-01T11:51:47Z [net] received: version (102 bytes) peer=2
2022-12-01T11:51:47Z [net] sending wtxidrelay (0 bytes) peer=2
2022-12-01T11:51:47Z [net] sending sendaddrv2 (0 bytes) peer=2
2022-12-01T11:51:47Z [net] sending verack (0 bytes) peer=2
2022-12-01T11:51:47Z [net] receive version message: /Satoshi:22.0.0/: version 70016, blocks=119313, us=<IP_ADDRESS>:47828, txrelay=1, peer=2
2022-12-01T11:51:47Z [net] added time data, samples 4, offset +0 (+0 minutes)
2022-12-01T11:51:47Z [net] received: wtxidrelay (0 bytes) peer=2
2022-12-01T11:51:47Z [net] received: sendaddrv2 (0 bytes) peer=2
2022-12-01T11:51:47Z [net] received: verack (0 bytes) peer=2
2022-12-01T11:51:47Z New outbound peer connected: version: 70016, blocks=119313, peer=2 (block-relay-only)
2022-12-01T11:51:47Z [net] sending sendcmpct (9 bytes) peer=2
2022-12-01T11:51:47Z [net] sending ping (8 bytes) peer=2
2022-12-01T11:51:47Z [net] sending getheaders (933 bytes) peer=2
2022-12-01T11:51:47Z [net] initial getheaders (119312) to peer=2 (startheight:119313)
2022-12-01T11:51:47Z [net] received: sendheaders (0 bytes) peer=2
2022-12-01T11:51:47Z [net] received: sendcmpct (9 bytes) peer=2
2022-12-01T11:51:47Z [net] received: sendcmpct (9 bytes) peer=2
2022-12-01T11:51:47Z [net] received: ping (8 bytes) peer=2
2022-12-01T11:51:47Z [net] sending pong (8 bytes) peer=2
2022-12-01T11:51:47Z [net] received: addrv2 (16 bytes) peer=2
2022-12-01T11:51:47Z [net] ignoring addrv2 message from block-relay-only peer=2
2022-12-01T11:51:47Z [net] received: getheaders (933 bytes) peer=2
2022-12-01T11:51:47Z [net] getheaders 119313 to end from peer=2
2022-12-01T11:51:47Z [net] sending headers (82 bytes) peer=2
2022-12-01T11:51:47Z [net] received: feefilter (8 bytes) peer=2
2022-12-01T11:51:47Z [net] received: feefilter of 0.00001000 BTC/kvB from peer=2
2022-12-01T11:51:47Z [net] received: pong (8 bytes) peer=2
2022-12-01T11:51:47Z [net] received: headers (82 bytes) peer=2
2022-12-01T11:51:47Z [net] sending sendheaders (0 bytes) peer=2
2022-12-01T11:51:47Z [net] received: feefilter (8 bytes) peer=1
2022-12-01T11:51:47Z [net] received: feefilter of 0.00001000 BTC/kvB from peer=1
2022-12-01T11:51:47Z [net] received: addrv2 (2955 bytes) peer=1
2022-12-01T11:51:47Z [net] Received addr: 158 addresses (158 processed, 0 rate-limited) from peer=1
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[543][54]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[280][41]
2022-12-01T11:51:47Z [addrman] Added [2001:470:67:601:ed0e:e0a5:895f:79a3]:38333 mapped to AS0 to new[22][51]
2022-12-01T11:51:47Z [addrman] Added [2600:1700:b360:c6f0:cd99:71b9:15aa:e286]:38333 mapped to AS0 to new[634][3]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[553][51]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[553][55]
2022-12-01T11:51:47Z [addrman] Added [2a0b:f4c0:16c:7::1]:38333 mapped to AS0 to new[813][41]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[234][30]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[955][37]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[147][12]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[847][27]
2022-12-01T11:51:47Z [addrman] Added [2001:ac8:9a:17::b54e]:38333 mapped to AS0 to new[468][51]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[456][44]
2022-12-01T11:51:47Z [addrman] Added [2001:861:8b40:db00:d0fa:dfcc:d3ea:d127]:18333 mapped to AS0 to new[486][7]
2022-12-01T11:51:47Z [addrman] Added [2601:646:a180:5330:d8a3:5229:7dc2:5c14]:38333 mapped to AS0 to new[864][53]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[883][17]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[813][63]
2022-12-01T11:51:47Z [addrman] Added [2a02:6ea0:cc1f:1::b61e]:38333 mapped to AS0 to new[337][17]
2022-12-01T11:51:47Z [addrman] Added [2604:5500:9065:ff00:7d24:b62e:33a0:6389]:38333 mapped to AS0 to new[777][24]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:8335 mapped to AS0 to new[847][25]
2022-12-01T11:51:47Z [addrman] Added <IP_ADDRESS>:38333 mapped to AS0 to new[994][50]

What version of Bitcoin Core are you using?
v24.0.1
Host operating system and version
Ubuntu 22.10
Host machine specifications
Intel i7, 64GB RAM, NVMe SSD

Looks nice! Is there a way to make the "Relevant log output" render with a click-to-expand button? I think it would make the issue easier to read. Maybe an option could be to add the collapsable markdown code template as an initial value of the field.

Ooooh that would be nice! I will investigate, but dunno if you can interleave a yaml object inside a markdown one...

(BTW I'm still changing the template a little bit on the input side, going to focus on the actual output afterwards :P)


Get the M of self-attn

The M obtained by the function _hide_other_subjects_from_subjects is all 0, which means that the result of self-attn is still the result of Q*K, not the result of bounded attention.
The results of subject_masks and background_masks obtained in function _hide_other_subjects_from_subjects are as follows：

That is right
However, after the following code operation, the returned sim_masks are all 0.

Great find. Thanks!
I fixed it now


[Bug]: Logging to both file and STDOUT

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[X] I have checked the troubleshooting section and my problem is not described there.
[X] I have read the changelog and my problem is not mentioned there.

Deploy method
Snap
Zwavejs2Mqtt version
v10
ZwaveJS version
v10.0.3
Describe the bug
Screencast from 31. aug. 2022 kl. 20.57 +0200.webm
To Reproduce
Tail the logfile (or even journald) at the same time as you have the «debugger» open in Z2M. I have «log to file» enabled.
Expected behavior
That it logs just to file, not to both.
Additional context
No response

Thinking about this again this has been the default behaviour since start. This because without the log to stdout the debugger wouldn't work


OTEL_EXPORTER_OTLP_HEADERS not honored by gRPC exporter

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

I noticed that the gRPC exporter does not honor OTEL_EXPORTER_OTLP_HEADERS (or variants) when setting up metadata, which makes it impossible to configure the gRPC exporter through env vars, if you need authentication metadata.
Based on the spec, I expected that environment variable to apply to the gRPC exporter:

Key-value pairs to be used as headers associated with gRPC or HTTP requests.

Am I misreading the spec, or is this an oversight?

I believe this is indeed an oversight, i implemented OTEL_EXPORTER_OTLP_HEADERS for http but i don't remember seeing that it was applicable to grpc too. Do you want to tackle this ?

Yep, I will work on a PR. Thanks for confirming!


How to apply PA for Elasticity problem.

Hi everybody!
I try to apply PA for Elasticity problem (ex2). I read this on the website (https://mfem.org/performance/) and I know this is not implement on the triangles or tetrahedra elements. I just want to apply for quadrilaterals. So I try coding the ex2 using the quadrilaterals mesh but it doesn't work. It returns: BilinearFormIntegrator::AssemblePA(...) is not implemented for this class. That does seem like PA currently does not support for Elasticity, right? Or I do not know. I hope someone will give me an answer. Thank you very much!!!

Hi @nghiakvnvsd,
We do not have a partial assembly formulation for linear elasticity in the library yet. We plan to add that in the future, so you can wait for that. Alternatively, you can try to develop it yourself, it should be doable once you familiarize yourself with other PA code, e.g. the one for diffusion.
I have copies @YohannDudouit and @dylan-copeland in case they have additional comments and suggestions.
Cheers,
Tzanio


p2pool: 2.1 -> 2.2.1

Description of changes
Changes since 2.1:

https://github.com/SChernykh/p2pool/releases/tag/v2.2
https://github.com/SChernykh/p2pool/releases/tag/v2.2.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 186642 run on x86_64-linux 1

1 package built:

p2pool


SHS-NG M4.1: Port environment page to new backend.

This change moves the environment page to the new UI module,
making modifications so that its data is stored in and retrieved
from the new store.
Some temporary internal API changes were made to maintain the current
code working when using the new UI implementation. These may be cleaned
up when the old UI code is cleaned up and only the new implementation
remains.

@squito I don't think there are any tests other than the ones I added here, which only cover the listener part.


App blank after gone from inactive to active

Sometime when the app has been left inactive in the background, it does not refresh and seem blank.

It is probably because of refreshing not working due to faulty app state when app goes from foreground to background, and then to foreground again.
We should be able to find and fix this by writing a unit test.


DPO for T5 problem , error:AttributeError: 'tuple' object has no attribute 'logits'

I am using official example (https://huggingface.co/blog/dpo-trl) to optimize T5 using DP0. Dataset  format is the same but I still get error: 'tuple' object has no attribute 'logits'
here is the code. Sorry I have no idea how to format the code. The code button does now work well.

Install everything
!pip install transformers --quiet
!pip install pandas nltk sentencepiece --quiet
!pip install datasets
!pip install evaluate
!pip install rouge_score
!pip install trl
from transformers import AutoTokenizer, AutoModelForSequenceClassification, AutoModelForSeq2SeqLM, GenerationConfig
from datasets import load_dataset
from trl import PPOTrainer, PPOConfig, AutoModelForSeq2SeqLMWithValueHead
from trl import create_reference_model
import torch
import evaluate
import numpy as np
import pandas as pd

Load model (I am using this paraphrasing model as an example)
model_name = "humarin/chatgpt_paraphraser_on_T5_base"
model = AutoModelForSeq2SeqLMWithValueHead.from_pretrained(
model_name, # location of saved SFT model
low_cpu_mem_usage=True,
torch_dtype=torch.float32,
load_in_4bit=False,
is_trainable=True
)
model_ref = AutoModelForSeq2SeqLMWithValueHead.from_pretrained(
model_name,  # same model as the main one
low_cpu_mem_usage=True,
torch_dtype=torch.float32,
load_in_4bit=False
)

Load and process dataset (I am using dataset used to train this paraphrasing model as an example)
def return_prompt_and_responses(samples): #-> Dict[str, str, str]:
return {
"prompt": [
"paraphrase: " + atext
for atext in samples["text"]
],
"chosen": [
apara[0]
for apara in samples["paraphrases"]
],
"rejected": [
aline
for aline in samples["text"]
]
}
dataset = load_dataset(
"humarin/chatgpt-paraphrases",
split="train[:1%]",
)
original_columns = dataset.column_names
dataset = dataset.map(
return_prompt_and_responses,
batched=True,
remove_columns=original_columns
)

Train the model
from transformers import Seq2SeqTrainer, Seq2SeqTrainingArguments,TrainingArguments
from trl import DPOTrainer, AutoModelForSeq2SeqLMWithValueHead
tokenizer = AutoTokenizer.from_pretrained("humarin/chatgpt_paraphraser_on_T5_base")
output_dir="dpo_model"
training_args = Seq2SeqTrainingArguments(
output_dir="11",
learning_rate=3e-4,
num_train_epochs=1,
per_device_train_batch_size=8,
per_device_eval_batch_size=8,
gradient_accumulation_steps=2,
)
dpo_trainer = DPOTrainer(
model,
model_ref,
args=training_args,
beta=0.1,
train_dataset=dataset,
#eval_dataset=eval_dataset,
tokenizer=tokenizer,
#peft_config=peft_config,
)
dpo_trainer.train()
dpo_trainer.save_model(output_dir)

So the error I get is: (AttributeError: 'tuple' object has no attribute 'logits')
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[20], line 31
     19 #from trl import DPOTrainer, AutoModelForSeq2SeqLMWithValueHead
     20 dpo_trainer = DPOTrainer(
     21     model,
     22     model_ref,
   (...)
     28     #peft_config=peft_config,
     29 )
---> 31 dpo_trainer.train()
     32 dpo_trainer.save_model(output_dir)

File /usr/local/lib/python3.10/dist-packages/transformers/trainer.py:1555, in Trainer.train(self, resume_from_checkpoint, trial, ignore_keys_for_eval, **kwargs)
   1553         hf_hub_utils.enable_progress_bars()
   1554 else:
-> 1555     return inner_training_loop(
   1556         args=args,
   1557         resume_from_checkpoint=resume_from_checkpoint,
   1558         trial=trial,
   1559         ignore_keys_for_eval=ignore_keys_for_eval,
   1560     )

File /usr/local/lib/python3.10/dist-packages/transformers/trainer.py:1860, in Trainer._inner_training_loop(self, batch_size, args, resume_from_checkpoint, trial, ignore_keys_for_eval)
   1857     self.control = self.callback_handler.on_step_begin(args, self.state, self.control)
   1859 with self.accelerator.accumulate(model):
-> 1860     tr_loss_step = self.training_step(model, inputs)
   1862 if (
   1863     args.logging_nan_inf_filter
   1864     and not is_torch_tpu_available()
   1865     and (torch.isnan(tr_loss_step) or torch.isinf(tr_loss_step))
   1866 ):
   1867     # if loss is nan or inf simply add the average of previous logged losses
   1868     tr_loss += tr_loss / (1 + self.state.global_step - self._globalstep_last_logged)

File /usr/local/lib/python3.10/dist-packages/transformers/trainer.py:2725, in Trainer.training_step(self, model, inputs)
   2722     return loss_mb.reduce_mean().detach().to(self.args.device)
   2724 with self.compute_loss_context_manager():
-> 2725     loss = self.compute_loss(model, inputs)
   2727 if self.args.n_gpu > 1:
   2728     loss = loss.mean()  # mean() to average on multi-gpu parallel training

File /usr/local/lib/python3.10/dist-packages/trl/trainer/dpo_trainer.py:500, in DPOTrainer.compute_loss(self, model, inputs, return_outputs)
    495 if not self.use_dpo_data_collator:
    496     warnings.warn(
    497         "compute_loss is only implemented for DPODataCollatorWithPadding, and you passed a datacollator that is different than "
    498         "DPODataCollatorWithPadding - you might see unexpected behavior. Alternatively, you can implement your own prediction_step method if you are using a custom data collator"
    499     )
--> 500 loss, metrics = self.get_batch_metrics(model, inputs, train_eval="train")
    502 # force log the metrics
    503 if self.accelerator.is_main_process:

File /usr/local/lib/python3.10/dist-packages/trl/trainer/dpo_trainer.py:451, in DPOTrainer.get_batch_metrics(self, model, batch, train_eval)
    443 """Compute the DPO loss and other metrics for the given batch of inputs for train or test."""
    444 metrics = {}
    446 (
    447     policy_chosen_logps,
    448     policy_rejected_logps,
    449     policy_chosen_logits,
    450     policy_rejected_logits,
--> 451 ) = self.concatenated_forward(model, batch)
    452 with torch.no_grad():
    453     if self.ref_model is None:

File /usr/local/lib/python3.10/dist-packages/trl/trainer/dpo_trainer.py:421, in DPOTrainer.concatenated_forward(self, model, batch)
    407 len_chosen = batch["chosen_labels"].shape[0]
    409 model_kwargs = (
    410     {
    411         "labels": concatenated_batch["concatenated_labels"],
   (...)
    415     else {}
    416 )
    417 all_logits = model(
    418     concatenated_batch["concatenated_input_ids"],
    419     attention_mask=concatenated_batch["concatenated_attention_mask"],
    420     **model_kwargs,
--> 421 ).logits.to(torch.float32)
    423 all_logps = self._get_batch_logps(
    424     all_logits,
    425     concatenated_batch["concatenated_labels"],
    426     average_log_prob=False,
    427 )
    429 chosen_logps = all_logps[:len_chosen]

AttributeError: 'tuple' object has no attribute 'logits'

@younesbelkada

hi @Oxi84
which version of TRL are you using?

Latest one. I installed using:
!pip install transformers
!pip install trl

Hmm T5 models should be supported for DPO since this PR: https://github.com/huggingface/trl/pull/586
And we do have tests that correctly test DPO correctness for T5 models: https://github.com/huggingface/trl/blob/main/tests/test_dpo_trainer.py#L78
Can you double check your TRL version?
>>> import trl
>>> trl.__version__
'0.7.3.dev0'

@younesbelkada
I get trl version: 0.7.2.
Do you any complete example with T5? I was not to find any. Just a few with PPO.

This is dataset, does not work even with one line so this is not a problem with padding:
Dataset({
features: ['chosen', 'rejected', 'prompt'],
num_rows: 1
})

Same issue,with BART is the issue fixed or anyone  have any solution to this?

Anyone did any model training with BART/T5 with DPO?

@lvwerra  can you please check

@younesbelkada  can you please check,this problem still exists

@Oxi84 is the problem solved at your end?

@Antimony5292 did you try DPO with T5? I found issues in using it ( look at issue #1025 ) ... Do you think that I can fix with this solution?

@Antimony5292 did you try DPO with T5? I has problems in using it ( look at issue #1025 ) ... Do you think that I can fix with this solution?

I've only tested it on the MarianMT, but I think it works just as well on the T5, so you might try it!


End to End Test

This PR adds two new packages

Add a contracts package - these are go binding to the two contracts that we have
Add a test package that performs an end to end test of the system.

The end to end test does the following

Setup a L1 Geth node (in memory) with the deposit feed contract, clique signing, a premine, and unlocked accounts.
Setup a L2 Geth node (in memory) with the L1Block Info contract
Configure the rollup node to point to the L1 and L2 Geth nodes (over http or ws).
Run the entire system.
Run a Deposit transaction against L1 Geth and verifies that the mint shows up in L2 Geth.

The test runs in about 3 seconds. The runtime could be lower & the test more reliable if I used a subscription to determine when the L2 head was updated (currently using a timer after the L1 transaction is confirmed).

Codecov Report

Merging #154 (13c3ca0) into main (b66529d) will increase coverage by 7.78%.
The diff coverage is 81.20%.

@@            Coverage Diff             @@
##             main     #154      +/-   ##
==========================================
+ Coverage   34.26%   42.04%   +7.78%
==========================================
  Files          11       13       +2
  Lines         750      899     +149
==========================================
+ Hits          257      378     +121
- Misses        468      488      +20
- Partials       25       33       +8

Impacted Files
Coverage Δ

opnode/test/geth.go
48.93% <48.93%> (ø)

opnode/test/setup.go
96.07% <96.07%> (ø)

Continue to review full report at Codecov.

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

I like the new ABI gen method better, but I need to change it so it also has the deployed byte code and place that directly into the genesis.


kde-applications: 18.08.1 -> 18.12.0

Motivation for this change
This is a preparation of the new kde applications release. Currently this uses the beta release, I will update to the stable on the final release :)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@ttuegel as it is released now, this pr is ready to be merged :)


Reduce warnings on CI from GitHub Actions

Looks like they're deprecating the node12 runtime for actions and are recommending node16 instead. Turns out basically every single action we have and reference uses node12, so this updates most of them to versions that use node16. I think we have some bytecodealliace-hosted actions to update as well but this should be the main crop.
I also updated the mdbook version here since I think the old version no longer compiles on newest rustc.

/bench_x64
just to make sure I didn't accidentally break that

Shows pct_change on x64 for the patch if merged compared to current head for main.
Pct_change is based on clocktick event cycles where the benchmarks are run with Sightglass.


Code Editor not working anymore

Describe the bug
Using the Code Editor is not working anymore.
The links for the script language selection are doing nothing and saving code using the modal button does also nothing.
Steps To Reproduce
Steps to reproduce the behavior:

create a new page
Click on Format > Code Editor
try to choose a script language
add some code
try to save

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): v0.28.2
PHP Version: PHP 7.3.7-1+0~20190710.40+debian10~1.gbp032aec
Hosting Method (Nginx/Apache/Docker): Apache on Debian Buster

Additional context
Console Log Errors when opening an existing Page or adding a new page in Bookstack:

Hi @Wachert,
Thanks for reporting that error. Seems to appear when there are no templates in the system. Easily fixed.
In regards to the code editor issue, I'm unable to replicate this as of yet.

Are you able to replicate this issue on the demo site?
What browser are you using to access BookStack?
Have you made any customisations to your BookStack instance?

1.) nope, on the demo site its working
2.) Chrome, Firefox, Vivaldi, Edge (we get this error on every browser, on different PCs)
3) nope not really, no plugins/mods, we tried updating to 0.28.2 which worked, but didn't fix the bug
We have updated using the release branch from git.

I installed bookstack yesterday and was using the code blocks with no issues.
Not complete but from my head:
PHP 7.2
Firefox
A looot of plugins for firefox.
Hosted on nginx.
Which language did you choose in the editor @Wachert ? I only used shell and nothing.

I have already problems clicking any language because nothing happens ;)
I also checked different browsers in case of maybe a browser plugin being the problem, but nope... even fresh browser dont work.
Maybe the installation has any problem but while the update, i got no errors.
I also deleted the cache once again using
php artisan cache:clear
php artisan view:clear

What i also did... rename the doc root Folder, create a blank one, reinstall bookstack, copy htaccess and env file into new installation and test again, but this also did not help.
Next thing i'll try: Backup the VM and update the VM and all packages.

OK i tried it but it also didn't help hm...

Darn, You definitely don't have any thing in the "Custom HTML Head Content" option in the settings area?

OOOH my god... i got'it, finally...
We have a Firewall (Sophos) which is also running virtual webservers (proxy) for DMZ Connections from the Web, and there an admin changed 2 options...

Deactivating these 2 options and everything works again as expected.
oooh man... sry ^^ and thanks for your help and tips.

@Wachert No problem, Happy to hear you found the cause!

I will further add that as soon as a Sophos UTM Firewall profile is loaded, it will stop working as well, as soon as static URL hardening is activated – even if there is an exceptions in place to skip the subnet the request is coming from.


Consolidate travis builds

There is a large fixed overhead of about O(7minutes) per travis run. We
seem to be limited to five build agents at a time so I consolidated the
.travis.yml into five builds. I tried to distribute the tasks fairly
evenly so that all of the builds take about the same amount of time. On
my personal travis build, where I only get three build agents, the total
run time of the build dropped to 50 minutes from one hour forty minutes.

[x] I've read the CONTRIBUTING guidelines

success :)


fix API mistake in The Model Factory section

In The Model Factory section, modelFactory.parse expects TemplateData instead of String as the first parameter.
context.getTemplateData().getTemplate() => context.getTemplateData()

You're right. Thanks!


Disposals Deathloops

Description
When you make a loop in disposals near the final exit it will catch and Gib everyone that goes in to it. With no possibility of escape.
It makes a awful spammy noise too as they are hitting the 4 corners so quickly.
Reproduction

Make a 4 corner disposals loop.
Jump in or throw a body in.
Wait until it gibs, gibs in about 1min.
All of the gibbed parts despawn, no brain drop.

Screenshots
Deathloop example

There are alternatives to it like this but at least this there is a bunch of work required and a chance to escape.

Additional context
Was mentioned in initial implementation for the corner damage on #21489 But it doesn't look like there is any mitigation for this.
The damage on corners its nice but maybe have it break after x hits to prevent deathloops, just a thought?

I will also note that the victim of the deathloop also ends up crashing around 30 seconds after being gibbed.

Since disposals damage was removed, this issue can be closed.


Is there a way to avoid slow cold start with the ray engine?

First execution of Modin with the ray engine seems very slow. My results and used code bellow.
from consts import csvDataSets
import pandas as pd
import modin.pandas as mpd
from modin.config import Engine
import ray
import time
from modin.config import BenchmarkMode
BenchmarkMode.put(True)

Engine.put("ray")
ray.init(runtime_env={'env_vars': {'__MODIN_AUTOIMPORT_PANDAS__': '1'}})

start = time.time()
brvehins1_df = pd.read_csv(csvDataSets + "brvehins1.csv")
end = time.time()
print(f'Pandas execution time: {end - start}')

for _ in range(5):
    start = time.time()
    brvehins1_df = mpd.read_csv(csvDataSets + "brvehins1.csv")
    end = time.time()
    print(f'Modin execution time: {end - start}')

The output:
Pandas execution time: 3.890420436859131
Modin execution time: 5.389143705368042
Modin execution time: 1.5507605075836182
Modin execution time: 1.4909210205078125
Modin execution time: 1.5514976978302002
Modin execution time: 1.5203297138214111

The csv is around 300 MB. My machine has i7-1165G7 with 32 GB of RAM. So neither is particularly extreme or specific in any way.
Is there any elegant way to avoid cold start short of just executing something?

@KrystofS thank you for reporting this issue. Unfortunately I don't know any good solutions for cold start with ray. It seems the first time each ray worker runs something, it will pay a startup cost. I'm going to mark this issue as a duplicate of #5157, a recent issue that describes nearly the same problem. Please follow that issue for updates.

Duplicate of #5157


Add doesNotContainKey/s to Guava Multimap asserts

Behavior matches the asserts for regular java.util Map asserts in core.

Thanks, we will review your PR shortly !

Thanks @ryber, first round of code review done, mostly minor stuff ;-)

@joel-costigliola feedback pushed up on its own commit. If you would rather I squash them and force push to the branch I can, or you can squash on merge, or you can leave them as different commits of course. I was not sure what your preference was. I think I got everything 😄

We usually squash the commits into one to make logical commits, cool if you do it but no problem if you let us

thanks @scordio updated with feedback applied

Thanks for your first contribution, @ryber!
We'll go ahead with the merge after releasing 3.25.2 (expected later this month).

@scordio oh sorry! I didn't catch that you suggested a name change. I went ahead and changed it

Thanks for your first contribution, @ryber!


pull request for e2e test at 12/31/2016 15:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Switched to imapclient, logging and refactoring for resilience

Fairly large refactoring.  I was getting regular EOF termination exceptions from the prior version, as well as upon restart, there was no check for unread mail that might have arrived while not running.
Upon investigating the cause/reading IMAP RFC's for idle mode, I came across the imapclient, which has built-in idle mode looping.
Full list of enhancements for your consideration :

Switched to imapclient for all email functionality including IDLE wait notification - default behavior is every 5 minutes we terminate the idle loop (configurable via settings)
Simplified imap connections to be minimal and restartable - the ```Imap`` class now keeps a single IMAP connection, switching into and out of IDLE mode as needed, querying unread, marking read etc, and also closing the connection in a timely fashion
Use python's logging facility - no longer using print() calls, now consistent logging across classes,  Verbosity is globally controlled via logging setLevel, so settings do not need to be passed around as well
namedtuple() data structures and separation of concerns refactoring - Separated out Rules class to process a EmailStruct namedtuple() collections, returning MatchResult collection.

Issues resolved by this PR:

Fatal terminations on prior IDLE loop processing would stop the application
Upon startup, existing unread mail was not queried/processed through our rules.  This change now always queries unread messages as part of the overall loop every IDLE timeout (default every 5 minutes) so worst-case delay in Gotify sending is minimized.
Prior version incorrectly might mark messages as read even though a Gotify send failure occured (thus missing a message). During the final phase of sending messages, Gotify classes send() returns list of EmailStructs that were successfully sent to Gotify, and thus can safely be marked as read in IMAP.

I have not had time to add tests/mocks, hope to do so in a future PR.  I have been running this version for over a week, and have seen several timeout exceptions (e.g. network drop or IMAP server disconnected) and this new version continues to reconnect without issue of hanging and never missing or delaying a message.

@andyloree I took time to cleanup a little with the help of tox.
This seems to works well for me also like this.
Tell me if you are ok with those commit and will merge then.

@andyloree I took time to fix little refactoring typo, and cleanup a little with the help of tox.
This seems to works well for me also like this.
Tell me if you are ok with those commit and will merge then.

These look great, excellent catches and fixes.  I will try to setup some mocks/unit testing as well in the near future.  Thanks again

I merge this MR so 👍🏻


Update message for attempting deletet on empty list

Fixes #126

LGTM! Can merge in after you merged master into this branch.


How do you reconstruct browser back history?

For example you have a form with 5 pages; If you return to this form after a while you want to resume on the same page you left;
So basically is:

On resume you go to resume page which calculates the page you left; Let's say page 4;
history.pushState of pages: 1, 2 and 3;
history.pushStatestate of the resume page url (If I don't do this, will mess up the router);
transition.to(page4);

Is there any better way to do this?
Thanks

Thanks for your question!
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
Questions like yours deserve a purpose-built Q&A forum. Could you post this question to Stack Overflow with the tag #react-router? https://stackoverflow.com/questions/ask?tags=react-router
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.


FancyZones doesn't remember layout for one monitr/duplicates settings

Microsoft PowerToys version
v0.60.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Have a 3 monitor setup.  Launch FancyZones Editor and specify a different layout for Monitor 3.  The layout assigned to Monitor 2 is always applied when closing.
✔ Expected Behavior
The ability to apply an individual layout to each monitor.  Works for Monitors 1 and 2, however Monitor 3 always reverts to match Monitor 2.
❌ Actual Behavior
The layout assigned to Monitor 2 is always applied to Monitor 3.
Other Software
No response

I'm also having this issue as of the most recent public release

I have three monitors (two 4K and one HD).
This issue occurs with my two 4K monitors and is quite frustrating

I have three monitors (two 4K and one HD). This issue occurs with my two 4K monitors and is quite frustrating

Yes, I have the same setup.  Should have clarified this, Thank you.  HD monitor will maintain its own FancyZone layout, the two 4K monitors always mimic the layout assigned to Monitor2.


Add build and push image CI

Signed-off-by: zhu733756<EMAIL_ADDRESS>Enhance https://github.com/fluent/fluentbit-operator/pull/210
Push images to the org like kubesphere after adding accounts with permissions. Suppose the tag is latest.

kubepshere/fluentbit-operator:latest with buildx(and64/arm64)
kubesphere/fluentbit:latest with amd64
kubesphere/fluentd:latest with amd64

Each pr after merged will push a new image.
/cc @patrick-stephens @benjaminhuo @wanjunlei @wenchajun Pls move here.

See https://github.com/zhu733756/fluentbit-operator/actions/runs/1880252411 and https://github.com/zhu733756/fluentbit-operator/actions/runs/1880252403


Feedback on Tutorial: Configuring Eclipse with SAP HANA Cloud Platform Tools for Java

Hello,
I've just tried three times to install HANA Cloud Plattform Tool and got every time the error:
An error occurred while collecting items to be installed
session context was:(profile=C__Users_d057430_eclipse_jee-mars_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.aspectj.runtime.source,<IP_ADDRESS>20507134200
No repository found containing: osgi.bundle,org.eclipse.contribution.weaving.jdt.source,2.2.0.e36x-20120507-1400
No repository found containing: org.eclipse.update.feature,org.eclipse.contribution.weaving.source,2.2.0.e36x-20120507-1400
No repository found containing: osgi.bundle,org.eclipse.contribution.xref.core.source,2.2.0.e36x-20120507-1400
No repository found containing: org.eclipse.update.feature,org.eclipse.contribution.xref.source,2.2.0.e36x-20120507-1400
No repository found containing: osgi.bundle,org.eclipse.contribution.xref.ui.source,2.2.0.e36x-20120507-1400
No repository found containing: osgi.bundle,org.eclipse.net4j.jms.api,3.0.0.v20110215-1551
Could you please fix it? Thanks a lot.
BR,
N.

It worked with Eclipse Neon.


remove dce5-dce5.md and reverse.md

Fix issues mentioned in #2018

cc @lemontrees123 @yitingdc

/lgtm


Invalid registry token store location

Dear all, I am writing here as I can't find the answer to my question anywhere and someone here might be able to help, although I understand that this error might not be caused by pyodbc and some windows layer behind. Thank you in advance for your precious help.
Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be sure to specify 32-bit Python or 64-bit:

Python: 3.11.4  64-bits
pyodbc: 4.0.39
OS: Windows 10 Enterprise
driver: CData ODBC Driver for SugarCRM

Issue
OperationalError: ('08001', "[08001] The registry token store localtion 'registry://' is invaild (-1) (SQLDriverConnect)")
after calling pyodbc.connect(<myconnstring>)
--> It seems my code (through Jupyter Notebook) can't access the registry, or rather that the registry location is wrong. I'm guessing the auth token cannot be stored, and hence the connexion fails to initialize, but I can't find where to specify another location to use.
The driver I'm using, CData ODBC Driver for SugarCRM, does work properly when connecting through the configuration software they provide on this machine. On the other hand, the exact same code works perfectly well from another machine to connect to the DB.
I tried to search for the error message (including the typos) online but I can't find anything...
Did anyone ever run into this issue, and know how to solve it?
Thank you

Not yet, but as I mentioned as far as I understand the problem is more linked to pyodbc/my python setup/ODBC windows drivers than the CData driver itself, given that I can connect properly with the UI they provide. The problem only appears when connection through pyodbc.
I’m guessing the problem boils down to being able to set the location to store the token… which I can’t find :(

I am connecting through a connexion string. As recommended here, I reached out to CData to ask about this issue, and they could solve my problem. For the ones running into it in the future, here is the solution:
Add the following parameter: OAuthSettingsLocation='C:\Users\Public\OAuthSettings.txt' (or any other location to which the current user has access to).
Thank you for your help!


Test whether it works on Windows

I have no idea whether the release actually works on Windows 64bit.

It works on windows 7 64 bits.

v1.2.1 doesn't work for me on Win Server 2008 or Win7 (both 64bit)
When run, a window appears with a dark grey background and nothing else.
Any ideas?

v1.2.1 doesn't work for me on Win Server 2008 or Win7 (both 64bit)
When run, a window appears with a dark grey background and nothing else.
Any ideas?

Hmmm not really. Perhaps it has to do with the way Appveyor CI builds it?
In the end it Electron under the hood but I could not find any issues doing a quick search that Electron has Windows 7 problem.
I am sorry that I probably can not help here because I am unable to replicate the issue without setting up Windows 😁

Thanks for the reply.
I've now unzipped directly to the root of C:\ and it is working.
Perhaps there were permissions issues on the directory I was using before.


Climate (thermostat) behavior for Auto mode

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.27.1
Python release (python3 --version):
3.4.2
Component/platform:
climate
ecobee 3
Description of problem:
The climate entity does not support auto mode correctly.  Auto mode should allow the user to set the cool set point (defined as high_temp in ecobee.py) and the heat set point (defined as low_temp in ecobee.py) for when the ecobee is set to be in auto mode.  Right now, it looks like the
ecobee component sets the high_temp and low_temp to be +/-1 of the temperature selected by the user using the input_slider.  That is really bad, I don't want my heat to come on at 70 and my AC to kick on at 72 if I had chose 71 as my target temperature in HA.
The functionality of Auto mode in HA should work the exact same way as using Auto mode in any thermostat app.  See the screenshot below.  The fire/snowflake icon at the top indicates that my thermostat is in Auto mode.  On the right, I am able to set the heating set point and the cooling set point separately.

Expected:
I expect to be able to set my heating set point and cooling set point separately when my thermostat is in Auto mode.
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
@justweb1 has implemented a paper range slider to allow a UI for setting the heating set point and cooling set point. https://github.com/home-assistant/home-assistant-polymer/pull/99

Some further clarification.
If I am in heat mode, I should only be able to see and set the heating set point (low_temp).

If I am in cool mode, I should only be able to see and set the cooling set point (high_temp).

Here is an example of the control that would be equal to a lot of thermostat apps.  The Cooling and Heating set point could be merged into one paper range slider.

This is actual a feature request, but it's been taken care of in #3189  :D


Error while parsing the file

i have been working with llamaparse for quite a while and never got this error until now.
some documents get parsed without problems, and others get this error (Error while parsing the file 'file path' : 'markdown') even though i was working with the same documents before and never had problems with it.
I even went llamaCloud and uploaded the documents there to test and still the same problem with the same documents i get this error (Result not found. Check job status to see if it has completed.)
here's one of those files if you want to test it:
test.pdf

Thansk for repporting!
Seems to have been a cache issue, for some reason the initial job parsing failed, and the error result were cached.
I re-run the job with invalidate_cache=true and the result came back as expected on this document.
In a future release (next week) we will make sure to handle this corner case so it never happen again


How to set the environment for AutoMLConfig?

Hello,
Is it possible to set an environment for AutoMLConfig? If possible, can you send an example, please?
I'm experiencing some version issues using compute instance (STANDARD_DS3_V2). I already tried to use conda env but the errors continue.
I looked in some forums and in the past there was the run_configuration parameter, but in the documentation it does not exist anymore.
Documentation: https://docs.microsoft.com/en-us/python/api/azureml-train-automl-client/azureml.train.automl.automlconfig.automlconfig?view=azure-ml-py
Old Example: https://github.com/solliancenet/Azure-Machine-Learning-Dev-Guide/blob/master/modeling/automl-regression-code-sample.md
Best regards,
Cristina

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 68a3df81-6871-c443-c413-16bb97982bd4
Version Independent ID: 5030fc51-ec28-d96e-fe85-a06a8fa1ce6f
Content: Regression tutorial: Automated ML - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-auto-train-models.md
Service: machine-learning
Sub-service: core
GitHub Login: @Aniththa
Microsoft Alias: anumamah

@crisansou we'll review your feedback and get back to you soon. Thanks.

Hi @crisansou, bringing your own environment to the AutoMLConfig is not a supported scenario. Can you provide additional detail as to what you're trying to accomplish by specifying a custom environment? Once we know more, we can loop in the appropriate contacts that might be able to help with your scenario.

Hi @nibaccam ,
I'm trying to set up an environment to use Azure AutoMl. First I created a compute instance STANDARD_DS3_V2. After that when running the experiment I got the error message undefined symbol: XGDMatrixSetDenseInfo. So I uninstalled the version that came on the machine (xgboost 1.3.3) and installed version 0.90 using the command !pip install xgboost==0.90 as suggested in this thread: https://docs.microsoft.com/en-us/answers/questions/322886/azure-machine-learning-services-automl-error-runni.html?childToView=325859#comment-325859.
The error of algorithm Xgboost was corrected, but now another one appeared: "Cannot serialize JSON, possibly due to NaN or Inf, scrubbing to zero and retrying ..."

The strange thing is that on my local machine the error does not occur.

In short, I don't know how to run the same code using an instance of Azure. Do you know where to find the requirements file? I saw that there is a file called "validated_linux_requirements.txt" on the VM, but when running it in a conda env other errors appeared.
Best regards,
Cristina

Hi @crisansou, bringing your own environment to the AutoMLConfig is not a supported scenario. Can you provide additional detail as to what you're trying to accomplish by specifying a custom environment? Once we know more, we can loop in the appropriate contacts that might be able to help with your scenario.

Hi @crisansou, you should be able to run your code on an Azure compute instance without errors. Please reach out to the<EMAIL_ADDRESS>alias so the product team can better assess if this is a bug within the Azure compute instance environment builds.

Hello @nibaccam ,
I sent the email, thank you!

Hi @crisansou, you should be able to run your code on an Azure compute instance without errors. Please reach out to the<EMAIL_ADDRESS>alias so the product team can better assess if this is a bug within the Azure compute instance environment builds.


Investigate crashes in the latest release

We have 3 crashes in the last release:
https://rink.hockeyapp.net/manage/apps/687667/app_versions/1/crash_reasons/203943413
https://rink.hockeyapp.net/manage/apps/687667/app_versions/1/crash_reasons/203947055 (possible fixed in #139)
https://rink.hockeyapp.net/manage/apps/687667/app_versions/1/crash_reasons/203942335 (possible fixed in #139)
It could happen because we somehow lose the path to the test folder (should also investigate this)

The issue seems to be fixed by fixing other crashes. In the last version we have 0 crashes.


Upgrade http 0.2 to http 1

Would it be possible to use a more recent version of http? from 0.2 to latest 1.1.0?
Right now we get an error with this crate if using a more recent version in our dependencies:
http::request::Request<Vec> = req.try_into_http_request(ctx).unwrap...
|       -------------------------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected Request<Vec<...>>, found Request<_>
note: Request<_> and Request<Vec<...>> have similar names, but are actually distinct types

Yes. I've been meaning to upgrade for a while now. I've just been waiting on reqwest (which I use for tests) to upgrade.
They recently merged the upgrade into master, but it is blocked on some other breaking changes.
I'm gonna upgrade it anyway and temporarily change the testing client to ureq until 0.12 is released. I'm tired of checking reqwest's status everyday.
This will be upgraded in #51, and a new release will be created after it is merged.

Thank you! I indeed noticed that Reqwest still use 0.2

For information:
On Reqwest side dev has been temp reverted here:
https://github.com/seanmonstar/reqwest/pull/2170
it's available on 0.12-dev


issubclass(jnp.float32, jnp.floating) does not work

Description
In [26]: issubclass(np.float32, np.floating)
Out[26]: True
In [27]: issubclass(jnp.float32, jnp.floating)
Out[27]: False

I expect the behavior to be consistent with numpy.
What jax/jaxlib version are you using?
head
Which accelerator(s) are you using?
No response
Additional System Info
No response

I think this is intended-ish. One of the main differences between numpy and JAX is that numpy has both scalar types (such as np.float32(0)) and array types (such as np.array(0, dtype=np.float32)). In JAX the decision was made early on to not have dedicated scalar types, but rather represent scalars as rank-zero arrays. Thus there is no such thing as a jax.numpy.float32 object, and jnp.float32 is just a convenience function to create a rank-0 array:
In [1]: import jax.numpy as jnp

In [2]: x = jnp.float32(0)

In [3]: type(x)
Out[3]: jaxlib.xla_extension.DeviceArray

That's the main reason that float32 and other scalar creation objects do not behave like numpy's scalar types.
A common pattern that we use in JAX instead is checking whether something is a subdtype:
In [4]: jnp.issubdtype(jnp.float32, jnp.floating)
OUt[4]: True

Would that work for your purposes?

I had a specific request from other users that there needs to be a superclass to jnp.float32 etc for a serialization use case. You want a superclass for jnp.float32 just for testing whether an object is a thing like jnp.float32.

Thanks! jnp.issubdtype works for my use case.

@hawkinsp we could probably make this happen by changing this: https://github.com/google/jax/blob/09a3796d5063940dc5e2402dea4e1bd89ffadfc1/jax/_src/numpy/lax_numpy.py#L170-L172
To something like this:
 def _make_scalar_type(np_scalar_type):
   meta = _ScalarMeta(np_scalar_type.__name__, (np_scalar_type.__mro__[1],),
                      {"dtype": np.dtype(np_scalar_type)})

This makes it so that issubclass(jnp.float32, jnp.floating) returns True, but I'm not sure whether it might have other side-effects...

So I looked into this... it's not going to be straightforward to fix. If we do the __bases__ solution, then np.dtype(jnp.float32) raises a warning because it's a non-recognized generic type. I tried deriving jnp.float32 from np.float32, but this causes issues because then jnp.float32 is a strict subdtype of np.float32, so for example issubdtype(jnp.float32, np.float32) returns False which breaks a bunch of user code. Additionally, we have workarounds for strange corner case behavior in np.issubdtype that no longer operate correctly (https://github.com/google/jax/blob/4746a39e59fc70caba161b00336b86687254df89/jax/_src/dtypes.py#L248-L253) and it's not obvious to me what the fix would be if jnp.float32 derives from np.generic.
As for the idea of making issubclass(_, jnp.floating) raise an error... that instancecheck override has to take place on the metaclass of the second argument, so for example we couldn't cause it to raise an error if the second argument were np.floating, and if we define a custom jnp.floating then numpy scalar types would no longer be subclasses of it, so things like issubclass(np.float32, jnp.floating) would return False.
All said, I think doing anything here is opening up a huge can of worms that will have subtle side-effects and ramifications for a lot of common usages; my judgment is that keeping the current behavior is probably best.
I'm going to close this issue – thanks for raising it!


WIP fixing the comments I missed in #227

I missed 15 code review comments from @nickjalbert in #227. So fixing them via this PR.
Don't merge yet. This is WIP

@nickjalbert feel free to look over the changes in response to your comments from the PR that I closed too early (#227) and either merge or give me the LGTM

LGTM!  Thanks for the fixes. :)


SSL Privacy Error

"This server could not prove that it is www.pathfinder-w.space; its security certificate is from dev.pathfinder-w.space. This may be caused by a misconfiguration or an attacker intercepting your connection.
You cannot proceed because the website operator has requested heightened security for this domain."

Just a matter of a deployment mis-configuration for TLS communications, not an actual software error. :)

Seems like a flub on the last deployment, and not an actual error with the code.
dev.pathfinder-w.space is the test bed for development features and links to Sisi.
Was this deployed unintentionally?

I made some changes to the Nginx config 2 days ago. I can´t see any problems with the Cert:
https://www.sslshopper.com/ssl-checker.html#hostname=www.pathfinder-w.space

It looks like the problem was fixed.


Calculated values are not respected in variables

Describe the bug
We use some simple calculated values to create certain spacing like:
4 + 2 = 6
{spacing.100} + {spacing.50} = 6
the result within the token is 6 but the value of the created variable is 0 (zero).
Expected behavior
The calculated value should be also the value of the variable.

I'm not able to reproduce

Are you sure your sets are setup correctly?

Can you share how you were able to reproduce? I have just tested with an alias in a different set and I was not able to reproduce

ah, i see - thank you for that extra context! 🙏
it seems we have an issue updating values when they contain math. in this case we'd expect that the variable would not use any reference but rather apply the final output value which is 6.

Fixed in 1.38 🚢


训练VeRi-Wild数据集时出现KeyError:"000001"错误

发生错误的日志是这样的，猜测是初始化camid时出错，但是看了代码之后没发现错误，如果有大佬知道的话，请告诉我一下，十分感谢
[07/25 08:27:32 fastreid]: Full config saved to /home/zhz/ll/code/reid/fast-reid/logs/veriwild/bagtricks_R50-ibn_4gpu/config.yaml
[07/25 08:27:32 fastreid.utils.env]: Using a generated random seed 32670587
[07/25 08:27:32 fastreid.engine.defaults]: Prepare training set
Traceback (most recent call last):
File "tools/train_net.py", line 57, in
args=(args,),
File "./fastreid/engine/launch.py", line 71, in launch
main_func(*args)
File "tools/train_net.py", line 42, in main
trainer = DefaultTrainer(cfg)
File "./fastreid/engine/defaults.py", line 201, in init
data_loader = self.build_train_loader(cfg)
File "./fastreid/engine/defaults.py", line 400, in build_train_loader
return build_reid_train_loader(cfg, combineall=cfg.DATASETS.COMBINEALL)
File "./fastreid/config/config.py", line 264, in wrapped
explicit_args = _get_args_from_config(from_config, *args, **kwargs)
File "./fastreid/config/config.py", line 292, in _get_args_from_config
ret = from_config_func(*args, **kwargs)
File "./fastreid/data/build.py", line 36, in _train_loader_from_config
data = DATASET_REGISTRY.get(d)(root=_root, **kwargs)
File "./fastreid/data/datasets/veriwild.py", line 53, in init
train = self.process_dir(self.train_list)
File "./fastreid/data/datasets/veriwild.py", line 67, in process_dir
camid = int(self.imgid2camid[imgid])
KeyError: '000001'

可能是你的数据集有问题

If your vehicle_info.txt does not have the header, then the code is trying to avoid the first row of that file, so you never register the image '000001". I coded a workaround, just change the following function on the file 'fastreid/data/datasets/veriwild.py':
    def process_vehicle(self, vehicle_info):
        imgid2vid = {}
        imgid2camid = {}
        imgid2imgpath = {}
        vehicle_info_lines = open(vehicle_info, 'r').readlines()

        #for idx, line in enumerate(vehicle_info_lines[1:]):
        for idx, line in enumerate(vehicle_info_lines):
            vid = line.strip().split('/')[0]
            imgid = line.strip().split(';')[0].split('/')[1]
            camid = line.strip().split(';')[1]
            img_path = osp.join(self.image_dir, vid, imgid + '.jpg')
            imgid2vid[imgid] = vid
            imgid2camid[imgid] = camid
            imgid2imgpath[imgid] = img_path

        #assert len(imgid2vid) == len(vehicle_info_lines) - 1
        assert len(imgid2vid) == len(vehicle_info_lines)
        return imgid2vid, imgid2camid, imgid2imgpath

Hope it works for you!


Disable 3D for root editor Viewport to curb tough-to-diagnose performance issues

The 3D scene is never visible from the root editor viewport since it's obscured by the editor GUI.
This can cause major performance issues with editor-enabled autoloads! I was wondering why the editor was stuttering so bad, but turns out that a depth-of-field effect was tanking the framerate with a large window! Eventually, I realized what might be happening, so I made a test scene that modifies the opacity of the editor's base control, and lo and behold, the scene was rendering behind it.
This shouldn't happen anyways (I've since switched to using EditorInterface.get_editor_viewport_2d as the parent of the visual nodes) but it's much tougher to diagnose than 2D, which will display in front of the editor GUI. Since the 3D scene would never be visible anyways, I think that it'd be best to disable it.

Do you have any idea why the root Viewport had DoF enabled? Is it sharing a WorldEnvironment with the 3D scene viewport?

I see. So this is only an issue because of the editor enabled autoload that you use. That makes sense.

I see. So this is only an issue because of the editor enabled autoload that you use. That makes sense.

Generally, yes. I'm not sure there are other use cases where this is likely to happen.
Another thing I'd like to say, although unrelated to this PR, is that I feel like autoloads should be children of the node that's actually used for the game. When running the game, that's the window, but in-editor, that's the 2D editor viewport. Is there any reason this shouldn't be the case? I'm sure that other people have the same need to have nodes within the editor world that exist outside of the edited scene. There's a slight possibility that some projects could break if this is changed, but given that accessing the root is typically done via the scene tree, it'd have to have been very unusual and hacky code to begin with... I doubt it'd be a problem (for 4.3 or 4.4 maybe.)


PropTypes for LayoutSupport components

Checkpoint for review before applying to any additional comps.
Fixes #900

Closing this - will revisit in Hooks world.


Synthetic request attribute should be set to false on browser-originated requests

Currently we only add the app.synthetic_request attribute to requests that come into frontend thru the load generator. We should make non-synthetic traffic show the false value.

Addressed in: https://github.com/open-telemetry/opentelemetry-demo/pull/631


Cannot connect to desktop app

Whenever I try to run :OpSignin, or any other :Op* command, I get the following error:
[ERROR] 2023/02/08 17:44:40 connecting to desktop app: read: connection reset, make sure the CLI is correctly installed
and Connect with 1Password CLI is enabled in the 1Password app

Things I've tried so far:

Double and triple checked requirements and installation instructions for op.nvim and onepassword-cli.
Tested the op command works fine outside of nvim.  It works fine.
Tested with biometric lock enabled, as well as token-based sessions.
Uninstall and reinstall op cli
Specifying op_cli_path in config

So far, nothing has helped.  I am on Arch Linux running neovim v0.8.3.  Not sure if it matters, but I am in a wayland desktop environment.
Thanks in advance!

This is an issue with the 1Password CLI/desktop app connection, not the Neovim plugin. Take a look at this and if you don’t have luck, feel free to reach out to 1Password’s excellent support team: https://developer.1password.com/docs/cli/get-started

I am seeing the same error, though it may be specific to Neovim+1Password CLI rather than this plugin.
I see the error when I try to run op from a neovim terminal, for example :!op signin or :term op signin. However, I do not get an error if I use the :term command to spawn a terminal and run op signin from there, or if I try those same commands from Vim.
It also happens only on Linux, not macOS.

Are you running a flatpak/AppImage of Neovim? Maybe it has to do with sandboxing?

I'm using bob-nvim to install Neovim nightly, currently on v0.9.0-dev-1319+g10baf8971.
I also have a version installed with the .deb package into /usr/bin/nvim, v0.9.0-dev-987+g371a74e4e, and that actually behaves differently: :!op signin and :term op signin, but :OpSignin gives the same "connection reset" error.

Can you try to provide a minimal init.lua to reproduce the issue? I have not been able to reproduce.

Also curious, what happens if you re-run the post-install hook? You can either uninstall and reinstall the plugin, or just cd to the plugin directory and run make install.
I'm wondering if it has something to do with the remote proxy process to the CLI.

Re-running the post-install hook didn't help. I tried making a minimal init.lua but sandboxing nvim while making 1password-cli work is hard.

Ok, I got the minimal init.lua working with the NVIM_APPNAME environment variable:
init.lua:
require('packer').startup(function(use)
    use 'wbthomason/packer.nvim'
    use({ 'mrjones2014/op.nvim', run = 'make install' })
end)

When running NVIM_APPNAME=nvim-test /usr/bin/nvim, :!op signin works without errors, but :OpSignin gives the connection reset error. :!op item get "Test" also works as expected.
When running NVIM_APPNAME=nvim-test nvim, (bob-nvim nightly installed in user home), both :!op signin and :OpSignin give the connection reset error.

Just to double check, your 1Password CLI is installed to /usr/local/bin/op correct? It must be installed here for the desktop app to be able to check its signature correctly.

It's installed in /usr/bin/op by the 1password .deb package, but works in the terminal and /usr/bin/nvim's shell so it seems like the desktop app can check the signature correctly.

I think I know the answer but just to make sure, you're using CLI v2, correct? What version of the CLI are you using?

Also you're not on aarch64-linux right? Currently there is only an x86_64-linux build of the backend process in the repo, but if needed I can add an aarch64-linux.

Just to update interested parties, I have not forgotten about this issue. I've been investigating the root cause.

I believe we've identified the issue, and it will hopefully be fixed by the next 1Password CLI version

Could yall check if this is still an issue with the latest version of 1Password CLI?

I'm seeing the issue with versions 2.18.0 and 2.19.0-beta.01.

Hmm, and you're using the latest 1Password desktop app version as well?

Using the beta version 8.10.8

Update: it worked!
I upgraded from 1Password for Linux 8.10.8 (81008013) to (81008042) and can now use op.nvim from nvim, and :!op signin works as well!

Awesome! Anyone else let me know if updating doesn’t work for you.


unable to run the setup

when i ran
sudo chmod +x setup.sh && ./setup.sh
i got this
./setup.sh: 5: ./setup.sh: Syntax error: "(" unexpected
then i gave the setup file 755 permission and ran
sudo bash setup.sh
i got this
sed: -e expression #1, char 56: unterminated s' command
sed: -e expression #1, char 70: unterminated s' command sed: -e expression #1, char 72: unterminated s' command
sed: -e expression #1, char 68: unterminated s' command setup.sh: line 33: docker-compose: command not found

Same here

Same issue in #28


Fix Null pointer exception in avoid default value switch parameter

Looks good to me.

Thanks. Merged.


Add Animation on scroll in Home page

Resolve #79

In scroll animation this problem is here please solve it


Non-English locales have a broken watermark

Attachments

image.png (26 KiB)

Originally written by chomp

Dupe

Originally written by chomp


Bias correction fix

Addresses #1968.
This PR updates the way masks are inherited from the forecast and truth cubes to the forecast_error. Rather than happening implicitly (as is currently the case), the propagation of masks is now performed explicitly.
Unit and acceptance tests were also updated to considered masked data (for both forecast and truth) to ensure the masks are passed on as expected.
The updated acceptance test data is included in https://github.com/metoppv/improver_test_data/pull/36.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Thanks @benowen-bom this addresses #1968. The addition of tests checking for masked arrays vs non-masked arrays is good. I have checked that the acceptance tests pass locally. I understand that @bomRob has run a suite on a workstation to check that the results are as expected.

Thanks @dmentipl for the review!