can't send sats

I haven't been able to send sats for a few days now. Not sure if it's Mutiny, could be the federation I'm in. Either way I can't send sats. I don't have a lot on my balance, thank goodness, but thought y'all should know.

Upload logs and we can take a look.

Apr 14, 2024, 7:46 PM by @.***:

Upload logs and we can take a look.
—
Reply to this email directly, > view it on GitHub https://github.com/MutinyWallet/mutiny-web/issues/1057#issuecomment-2054225107> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/BHUOMEGG77TMGJKDYYMTSJDY5MINTAVCNFSM6AAAAABGGLXTCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGIZDKMJQG4> .
You are receiving this because you authored the thread.> Message ID: > <MutinyWallet/mutiny-web/issues/1057/2054225107> @> github> .> com>

ad15 2024-04-15 00:00:06.548 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:06.548 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:07.565 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:07.565 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:07.565 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:08.565 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:08.565 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:08.565 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:09.582 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:09.582 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:09.582 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:10.365 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:00:10.582 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:10.598 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:10.598 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:11.582 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:11.582 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:11.582 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:12.615 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:12.615 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:12.615 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:12.665 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:00:12.665 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:00:12.665 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:12.665 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:00:13.615 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:13.632 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:13.632 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:14.632 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:14.632 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:14.632 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:15.632 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:15.649 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:15.649 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:16.649 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:16.649 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:16.649 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:16.782 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:00:16.782 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:17.649 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:17.649 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:17.649 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:18.665 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:18.665 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:18.665 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:19.665 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:19.665 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:19.665 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:20.682 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:20.682 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:20.682 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:21.682 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:21.682 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:21.682 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:22.699 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:22.699 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:22.699 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:22.782 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:00:22.782 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:00:22.782 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:22.782 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:00:23.165 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:00:23.165 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:23.515 INFO  [mutiny_core::nodemanager:657] Updated fee estimates!
ad15 2024-04-15 00:00:23.515 TRACE [lightning_transaction_sync::esplora:92] Starting transaction sync.
ad15 2024-04-15 00:00:23.715 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:23.715 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:23.715 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:23.849 DEBUG [lightning_transaction_sync::esplora:234] Finished transaction sync at tip<PHONE_NUMBER>0000000000dd53113062393ad899a2e540f28af3f0a92e94922ccc: 0 confirmed, 0 unconfirmed.
ad15 2024-04-15 00:00:23.982 INFO  [mutiny_core::nodemanager:1207] We are synced!
ad15 2024-04-15 00:00:24.715 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:24.715 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:24.715 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:25.715 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:25.715 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:25.715 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:29.016 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:29.016 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:29.016 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:30.016 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:30.032 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:30.032 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:30.882 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:30.882 ERROR [mutiny_core::nostr::nwc:356] failed to pay invoice: Payment timed out.
ad15 2024-04-15 00:00:31.016 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:31.016 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:00:31.016 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:00:31.882 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:31.882 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:32.149 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:32.149 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:32.149 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:32.199 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:32.199 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:32.199 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:32.299 TRACE [mutiny_core::federation:917] Done with stream outcome, status: Pending
ad15 2024-04-15 00:00:32.982 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:32.982 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:00:32.982 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:00:32.982 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:32.982 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:00:33.316 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:33.316 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:33.316 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:33.366 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:33.382 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:33.382 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:33.382 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:33.549 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:34.866 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:34.866 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:34.866 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:34.916 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:34.916 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:34.916 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:34.932 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:34.982 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:35.982 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:35.982 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:35.982 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:36.066 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:36.082 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:36.082 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:36.082 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:36.116 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:37.116 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:37.132 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:37.132 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:37.199 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:37.199 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:37.199 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:37.199 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:37.249 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:38.366 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:38.366 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:38.366 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:38.416 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:38.416 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:38.416 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:38.432 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:38.449 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:38.816 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:00:38.816 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:39.482 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:39.482 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:39.482 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:39.532 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:39.532 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:39.532 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:39.532 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:39.582 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:40.499 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:00:40.582 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:40.599 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:40.599 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:40.666 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:40.682 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:40.682 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:40.682 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:40.716 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:41.732 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:41.749 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:41.749 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:41.832 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:41.832 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:41.832 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:41.832 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:41.882 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:42.866 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:42.882 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:42.882 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:42.966 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:42.982 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:42.982 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:42.982 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:43.032 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:43.099 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:00:43.099 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:00:43.099 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:43.099 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:00:43.482 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:00:43.482 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:44.032 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:44.032 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:44.049 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:44.099 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:44.099 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:44.099 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:44.099 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:44.132 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:45.149 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:45.149 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:45.149 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:45.216 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:45.216 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:45.216 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:45.216 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:45.249 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:46.116 WARN  [mutiny_core::nostr:1982] Skipping event: 20b5bfab80c2c1e9f053a6d73759bafc6faa4284693739ce16102d8f08af3fdc
ad15 2024-04-15 00:00:46.116 WARN  [mutiny_core::nostr:1982] Skipping event: d9a874a007c5e21557e86f1f197c6817f08019459f5e38f73d181a90f390e88c
ad15 2024-04-15 00:00:46.116 WARN  [mutiny_core::nostr:1982] Skipping event: 8eca3384be9a255110814dc01e6eda291a3f29471cf1c018fb0bf714be4df567
ad15 2024-04-15 00:00:46.116 WARN  [mutiny_core::nostr:1982] Skipping event: c9f6a7d76e1572beb3c27d78f0ed76af75fa4ffb75bc6209893d1cb857a1d6c2
ad15 2024-04-15 00:00:46.116 WARN  [mutiny_core::nostr:1982] Skipping event: 773e22b5ac6ece5feded40a97a501015fb4141c123c9a2bcae3068770520bcb1
ad15 2024-04-15 00:00:46.249 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:46.249 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:46.249 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:46.316 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:46.333 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:46.333 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:46.333 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:46.366 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:47.366 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:47.366 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:47.366 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:47.433 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:47.433 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:47.433 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:47.449 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:47.483 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:48.483 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:48.483 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:48.483 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:48.566 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:48.583 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:48.583 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:48.583 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:48.616 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:49.616 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:49.616 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:49.616 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:49.699 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:49.699 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:49.699 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:49.716 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:49.749 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:50.766 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:50.766 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:50.766 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:50.849 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:50.849 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:50.849 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:50.866 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:50.883 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:51.233 TRACE [lightning_background_processor:693] Pruning and persisting network graph.
ad15 2024-04-15 00:00:51.899 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:51.899 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:51.899 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:51.983 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:51.983 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:51.983 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:51.999 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:52.049 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:53.049 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:53.049 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:53.049 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:53.116 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:53.116 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:53.116 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:53.133 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:53.166 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:53.249 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:00:53.249 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:00:53.249 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:00:53.249 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:00:53.849 ERROR [mutiny_core::nodemanager:359] Error setting device lock: Network connection closed.
ad15 2024-04-15 00:00:54.166 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:54.166 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:54.166 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:54.249 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:54.266 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:54.266 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:54.266 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:54.299 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:55.216 TRACE [lightning_background_processor:693] Calling ChannelManager's timer_tick_occurred
ad15 2024-04-15 00:00:55.216 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:00:55.216 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:00:55.316 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:55.316 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:55.316 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:55.399 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:55.399 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:55.399 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:55.416 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:55.449 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:56.466 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:56.466 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:56.466 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:56.516 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:56.516 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:56.516 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:56.533 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:56.549 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:57.566 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:57.566 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:57.566 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:57.649 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:57.649 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:57.649 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:57.649 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:57.683 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:58.699 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:58.716 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:58.716 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:58.783 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:58.783 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:58.783 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:58.783 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:58.799 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:00:59.816 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:00:59.816 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:00:59.816 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:00:59.883 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:00:59.883 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:00:59.883 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:00:59.899 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:00:59.933 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:00.349 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:01:00.349 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:00.933 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:00.949 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:01:00.949 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:01:01.016 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:01:01.033 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:01:01.033 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:01:01.033 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:01:01.066 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:01.883 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:01.883 ERROR [mutiny_core::nostr::nwc:356] failed to pay invoice: Payment timed out.
ad15 2024-04-15 00:01:02.083 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:02.083 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:01:02.083 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:01:02.183 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:01:02.183 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:01:02.183 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:01:02.183 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:01:02.216 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:03.216 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:03.233 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:01:03.233 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:01:03.316 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:01:03.333 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:01:03.333 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:01:03.333 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:01:03.366 TRACE [mutiny_core::federation:901] Streamed Outcome received: WaitingForRefund { block_height: 839759, gateway_error: GatewayInternalError { error_code: Some(400), error_message: "Error while paying lightning invoice. Outgoing contract will be refunded." } }
ad15 2024-04-15 00:01:03.366 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:03.633 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:01:03.633 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:01:03.633 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:03.633 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:01:04.183 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:01:04.183 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:04.366 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:04.383 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:01:04.383 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:01:04.450 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:01:04.466 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:01:04.466 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:01:04.466 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:01:04.483 TRACE [mutiny_core::federation:901] Streamed Outcome received: WaitingForRefund { block_height: 839759, gateway_error: GatewayInternalError { error_code: Some(400), error_message: "Error while paying lightning invoice. Outgoing contract will be refunded." } }
ad15 2024-04-15 00:01:04.533 TRACE [mutiny_core::federation:917] Done with stream outcome, status: InFlight
ad15 2024-04-15 00:01:05.650 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:05.666 TRACE [mutiny_core::federation:399] pending invoices, going to list operations
ad15 2024-04-15 00:01:05.666 TRACE [mutiny_core::federation:417] About to go through 43 operations
ad15 2024-04-15 00:01:05.716 TRACE [mutiny_core::federation:439] Going through 1 pending invoices to extract status
ad15 2024-04-15 00:01:05.716 TRACE [mutiny_core::federation:896] start timeout stream futures
ad15 2024-04-15 00:01:05.716 TRACE [mutiny_core::federation:901] Streamed Outcome received: Created
ad15 2024-04-15 00:01:05.733 TRACE [mutiny_core::federation:901] Streamed Outcome received: Funded
ad15 2024-04-15 00:01:05.750 TRACE [mutiny_core::federation:901] Streamed Outcome received: WaitingForRefund { block_height: 839759, gateway_error: GatewayInternalError { error_code: Some(400), error_message: "Error while paying lightning invoice. Outgoing contract will be refunded." } }
ad15 2024-04-15 00:01:05.800 TRACE [mutiny_core::federation:901] Streamed Outcome received: Refunded { gateway_error: GatewayInternalError { error_code: Some(400), error_message: "Error while paying lightning invoice. Outgoing contract will be refunded." } }
ad15 2024-04-15 00:01:05.800 TRACE [mutiny_core::federation:905] Streamed Outcome final, returning
ad15 2024-04-15 00:01:05.800 TRACE [mutiny_core::federation:917] Done with stream outcome, status: Failed
ad15 2024-04-15 00:01:05.800 DEBUG [mutiny_core::federation:473] Saving updated payment
ad15 2024-04-15 00:01:06.800 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:06.800 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:06.800 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:08.200 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:08.216 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:08.216 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:15.100 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:15.133 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:15.133 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:15.266 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:01:15.266 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:01:15.266 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:15.266 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:01:15.266 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:01:16.133 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:16.133 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:16.133 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:17.116 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:17.133 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:17.133 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:18.133 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:18.133 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:18.133 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:19.150 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:19.150 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:19.150 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:20.167 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:20.167 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:20.167 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:21.267 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:21.267 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:21.267 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:22.267 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:22.267 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:22.267 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:22.317 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:01:22.317 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:23.283 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:23.300 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:23.300 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:24.300 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:24.300 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:24.300 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:27.083 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:27.083 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:27.083 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:28.100 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:01:28.117 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:01:28.117 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:28.117 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:01:28.500 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:01:28.500 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:31.333 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:31.333 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:31.333 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:33.350 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:33.367 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:33.367 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:37.567 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:37.567 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:37.567 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:42.834 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:42.834 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:42.834 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:51.167 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:51.167 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:51.167 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:52.184 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:01:52.184 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:01:52.184 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:52.184 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:01:52.601 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:01:52.601 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:01:54.234 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:54.267 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:54.267 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:01:54.484 TRACE [mutiny_core::storage:961] Trace: checking payment key: payment_inbound/448076568ac605ec5b15ecfcb8626f2fdca23cf31fe3e3854e06fc67d56be4e7
ad15 2024-04-15 00:01:54.484 TRACE [mutiny_core::storage:961] Trace: checking payment key: payment_outbound/448076568ac605ec5b15ecfcb8626f2fdca23cf31fe3e3854e06fc67d56be4e7
ad15 2024-04-15 00:01:54.484 TRACE [mutiny_core::federation:486] get_invoice_by_hash
ad15 2024-04-15 00:01:54.484 TRACE [mutiny_core::storage:961] Trace: checking payment key: payment_inbound/448076568ac605ec5b15ecfcb8626f2fdca23cf31fe3e3854e06fc67d56be4e7
ad15 2024-04-15 00:01:54.484 TRACE [mutiny_core::storage:961] Trace: checking payment key: payment_outbound/448076568ac605ec5b15ecfcb8626f2fdca23cf31fe3e3854e06fc67d56be4e7
ad15 2024-04-15 00:01:54.484 ERROR [mutiny_core::federation:492] could not get invoice by hash: Resource Not found.
ad15 2024-04-15 00:01:55.484 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:01:59.667 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:01:59.684 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:01:59.684 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:00.701 TRACE [lightning_background_processor:693] Calling ChannelManager's timer_tick_occurred
ad15 2024-04-15 00:02:00.701 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:02:00.701 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:02:00.701 TRACE [lightning_background_processor:693] Calling time_passed and persisting scorer
ad15 2024-04-15 00:02:04.917 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:04.934 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:04.934 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:05.934 INFO  [mutiny_core::nodemanager:657] Updated fee estimates!
ad15 2024-04-15 00:02:05.934 TRACE [lightning_transaction_sync::esplora:92] Starting transaction sync.
ad15 2024-04-15 00:02:06.267 DEBUG [lightning_transaction_sync::esplora:234] Finished transaction sync at tip<PHONE_NUMBER>0000000000dd53113062393ad899a2e540f28af3f0a92e94922ccc: 0 confirmed, 0 unconfirmed.
ad15 2024-04-15 00:02:06.434 INFO  [mutiny_core::nodemanager:1207] We are synced!
ad15 2024-04-15 00:02:09.101 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:09.118 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:09.118 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:10.118 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:02:10.118 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:02:10.118 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:10.118 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:02:10.534 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:02:10.534 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:11.134 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:11.151 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:11.151 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:15.368 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:15.368 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:15.368 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:17.518 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:17.534 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:17.534 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:19.551 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:19.568 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:19.568 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:22.718 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:22.734 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:22.734 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:24.884 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:24.901 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:24.901 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:25.901 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:02:25.901 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:02:25.901 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:25.901 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:02:27.951 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:27.968 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:27.968 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:28.135 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:02:28.135 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:31.118 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:31.135 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:31.135 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:35.301 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:35.318 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:35.318 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:36.318 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:02:37.335 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:37.351 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:37.351 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:41.501 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:41.518 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:41.518 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:45.735 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:45.752 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:45.752 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:46.752 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:02:46.752 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:02:46.752 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:46.752 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:02:49.768 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:02:49.785 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:02:52.968 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:52.985 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:52.985 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:02:58.035 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:02:58.052 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:02:58.052 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:01.202 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:01.219 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:01.219 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:05.402 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:05.402 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:05.402 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:09.502 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:09.519 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:09.519 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:10.519 TRACE [lightning_background_processor:693] Calling ChannelManager's timer_tick_occurred
ad15 2024-04-15 00:03:10.519 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:03:10.519 TRACE [mutiny_core::fees:177] Got fee rate from saved cache!
ad15 2024-04-15 00:03:10.519 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:03:10.519 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:03:10.519 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:03:10.519 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:03:11.452 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:03:11.452 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:03:12.685 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:12.685 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:12.685 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:13.702 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:03:15.852 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:15.869 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:15.869 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:17.886 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:17.902 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:17.902 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:22.069 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:22.086 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:22.086 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:26.286 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:26.302 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:26.302 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:30.469 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:30.486 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:30.486 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:31.486 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:03:31.486 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:03:31.486 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:03:31.486 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:03:32.486 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:32.519 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:32.519 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:33.269 TRACE [mutiny_core::networking::socket:62] received binary data from websocket: 38
ad15 2024-04-15 00:03:33.269 TRACE [lightning::ln::peer_handler:1632] Received message Pong(Pong { byteslen: 0 }) from 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:03:36.686 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:36.703 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:36.703 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:39.836 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:39.853 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:39.853 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:44.053 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:44.069 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:44.069 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:48.236 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:48.253 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:48.253 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:49.270 TRACE [lightning_background_processor:693] Calling OnionMessageHandler's timer_tick_occurred
ad15 2024-04-15 00:03:49.270 TRACE [lightning_background_processor:693] Calling PeerManager's timer_tick_occurred
ad15 2024-04-15 00:03:49.270 TRACE [lightning::ln::peer_handler:1279] Enqueueing message Ping { ponglen: 0, byteslen: 64 } to 03aefa43fbb4009b21a4129d05953974b7dbabbbfb511921410080860fca8ee1f0
ad15 2024-04-15 00:03:49.270 TRACE [mutiny_core::networking::proxy:92] sent data down websocket
ad15 2024-04-15 00:03:50.270 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:50.286 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:50.286 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:51.286 TRACE [lightning_background_processor:693] Rebroadcasting monitor's pending claims
ad15 2024-04-15 00:03:54.453 TRACE [mutiny_core::federation:368] Getting activity
ad15 2024-04-15 00:03:54.470 TRACE [mutiny_core::federation:417] About to go through 0 operations
ad15 2024-04-15 00:03:54.470 TRACE [mutiny_core::federation:439] Going through 0 pending invoices to extract status
ad15 2024-04-15 00:03:54.970 TRACE [mutiny_core::networking::socket:62] received binary da

Seems like the same issue as #1041
Which federation are you apart of?

Bitcoin Atlantis

Federation ID: 120879c1233789679a4ed9b47ba557f8da3d4577b4e0b3f61fa5afd3137b824a
Apr 15, 2024, 12:05 AM by @.***:

Seems like the same issue as > #1041 https://github.com/MutinyWallet/mutiny-web/issues/1041
Which federation are you apart of?
—
Reply to this email directly, > view it on GitHub https://github.com/MutinyWallet/mutiny-web/issues/1057#issuecomment-2054887168> , or > unsubscribe https://github.com/notifications/unsubscribe-auth/BHUOMEFRE6JIGKERM4LKIYLY5NGZLAVCNFSM6AAAAABGGLXTCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUHA4DOMJWHA> .
You are receiving this because you authored the thread.> Message ID: > <MutinyWallet/mutiny-web/issues/1057/2054887168> @> github> .> com>

Closing this one in favor of https://github.com/MutinyWallet/mutiny-web/issues/1041 which is the same issue. Please monitor that one.


add Account ID to the get_transactions() function

Would it be possible to add an account ID/name to the get_transactions() function? I have tried to play around with it myself and haven't found a way to do it, but I have never worked with gql, so I'm hoping your expertise can resolve it.
If adding a new field isn't an option, would pulling transactions for specific account IDs be an option?

@dsteiner10, this should be working now!  If you're using this library via pip, pip install --upgrade monarchmoney should get you the latest.

@hammem Thank you for such a fast response!


[SD CHANGE] FCS_STO_EXT.1 implemented test

What is the change request for the SD? Please describe.
It seems strange that the only test for this requirement is if the TOE uses platform storage. I would expect there to be something about verifying the location of the credentials (i.e. folder/database, etc) and that the evaluator would at least check that this data isn't in plain text.
Describe the solution you'd like
Add a set of test steps to verify the location of the stored credentials and to check they are not stored in plain text (since they are supposed to be stored by some encryption or conditioning).
One of the steps could also be that things like file permissions on the location are proper (i.e. not open to anyone but limited to whatever restricted account or controls are in place). This would seem to be important to check if the TOE is implementing the storage itself.
Describe alternatives you've considered
none
Additional context
none

There is also no test in the NIAP App Sw PP. While we are not opposed to additional test coverage, we are uncertain of how to author a test case that would provide assurance without mandating source code access or review.
Also, all files created by the application are subject to the file permissions test in FMT_CFG_EXT.1.2


I29 31 improve documentation

Closes issue #31

Codecov Report

Merging #33 (1c64768) into main (51ec299) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #33   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          715       715
=========================================
  Hits           715       715

Impacted Files
Coverage Δ

epimodels/_setup_matrices.py
100.00% <ø> (ø)

epimodels/inference/phe_inference.py
100.00% <ø> (ø)

epimodels/phe_model.py
100.00% <ø> (ø)

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 51ec299...1c64768. Read the comment docs.


feature/68 - fix dateHistogram and test

Fixes #68
Description

No idea what happened, but neither dateHistogram nor its test were right on master.

Fails

:no_entry_sign:
This PR has failing tests. Please alleviate the errors and commit them

result should output the expected query and results
expected { Object (entries) } to deeply equal { Object (entries) }

Warnings

:warning:

Your PR has lint warnings. Please consider fixing these.

dateHistogram.js
src/example-types/dateHistogram.js
'x' is defined but never used.
Line 49: ...keysToObject(x => 1, include),

:warning:
The README has not been updated. Please update the README.

Messages

:book:
Could not find any browser results.

  Generated by :no_entry_sign: dangerJS against 430397d295ca65ca6fd48f23b1659a84c9ffa55c

@Akrion npm run test and npm run test:ci both pass everything locally. I'm stumped. Any ideas?

seems to be some issue running the tests at all if you go find it on circle:
><EMAIL_ADDRESS>test:ci /home/circleci/project
> ./node_modules/mocha/bin/_mocha --recursive --reporter json > test-results.json

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:ci: `./node_modules/mocha/bin/_mocha --recursive --reporter json > test-results.json`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:ci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/circleci/.npm/_logs/2020-03-18T20_28_40_494Z-debug.log

Exited with code exit status 1

tests also pass as low as node 8.9.0, Circle is on latest 9

ok, it really is supposedly my code since taking out the test gets me a pass. But test:ci passes that code locally.

OK, duti is now in an error state, but it's not reporting an error on any test.

Fails

:no_entry_sign:
This PR has failing tests. Please alleviate the errors and commit them

result should output the expected query and results
expected { Object (entries) } to deeply equal { Object (entries) }

Warnings

:warning:
The README has not been updated. Please update the README.

Messages

:book:
Could not find any browser results.

  Generated by :no_entry_sign: dangerJS against 2b9447e03cf92ca521fd028ea4a14ab8a4cc3f7a

OK, I actually think I get it: it is my test, and it's a timezone issue that's making the expected keys on the output data different when you run it in different timezones

@stellarhoof @Akrion figured it out, Circle was fine, the keys on the histogram are timestamps so they were different when it ran on CI than when you run it locally. Altered the test to not be sensitive to timezone. Ready for review.

@doug-patterson awesome. Great detective work 👍

@Akrion I don't have merge permissions on this repo -- could you merge unless you want a second opinion?

@doug-patterson yeah I was hoping someone else would also take a look as well just in case. It has been awhile since I dealt with this repo.

sounds like we're good to go -- thanks for looking.

also, the companion PRs are tiny and could use a look if you've got the time


Do not render a component if it is hidden?

Potential performance enhancement.
For example, the navigator is hidden on mobile displays, but we still render it - we may be able to improve performance by not rendering hidden components.

I have managed to get this to work with the navigator and it seems to be hitting 60fps quite comfortably - my approach uses a util function to deduce whether a selection is visible before rendering:
function nav(selection) {
    if (util.isVisible(selection)) {
        var model = selection.datum();
        ....

Would this be ok or would we prefer to do something at app.js level?

Great stuff, how about extending d3.selection() to add a convenience method for this?
// Not sure about the name... any better ideas?
d3.selection.prototype.callIfVisible = function(callback) {
    // if selection is visible, call, otherwise don't
};

If this seems reasonable, I think it makes most sense to do it app.js.


feat(Data Mapper): Change Command Bar UI

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Please Include Screenshots or Videos of the intended change:

Things to Consider:

Previously discussed: should save button ever be disabled?

Should "generate XSLT" button be disabled when save is disabled?

Seems like leaving the button as the "selected" state is impossible

-> should we manually change the style to imitate "selected" state?

-> If so, where to get the background color/border radius such values (i.e. theme?)


optimize(http1): try parse response even if get writing errors

What type of PR is this?
optimize
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
HTTP/1.1 client场景，尝试在写请求失败后做一次响应体解析
(Optional) More detail description for this PR(en: English/zh: Chinese).

en: For now, when hertz client is processing http/1.1 requests, if the connection is closed by the peer during the process of writing body, it will directly return the broken pipe error to the caller (the caller is actually confused when he gets this error) , this case often occurs in the scenario of writing an oversized packet that exceeds the size allowed by the server. Generally, the server side decides not to continue receiving packets after parsing the header. Generally, a 400 error & a body will be written back, and then The connection is closed. This optimization strategy is to make a parsing attempt of the response before returning the error to the caller for the case of writing half of the error. If a valid response is obtained, the response will be returned first instead of the bare connection error message.
zh(optional): 目前hertz client 在处理http/1.1的请求的时候如果在写body的过程中，连接就被对端关闭了会直接将broken pipe 报错返回给调用者（调用者拿到这个错误其实是比较迷茫的），这个case 常出现在写一个超大包，超出server允许的大小的场景，一般是server侧解析完header之后决定不再继续收包了，一般会写回一个400的错误 + 一个body文案，之后就关闭连接了。Client 的优化的策略是，针对这种写一半报错的case，在返回错误给调用者之前，做一次response的解析尝试，如果拿到一个valid的response，优先返回这个response而不是裸的连接错误信息。
Which issue(s) this PR fixes:
None

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Update:

Add a protection read timeout to avoid potential infinite loop.
Adjust the non-sendfile error using standard network when writing request.

PTAL @wzekin @FGYFFFF @li-jin-gou

LGTM


 Parsing numbers (or integers at least) isn't something you should have to avoid or hack around. We should investigate reducing its deployed footprint—its main capabilities (parsing Factor number syntax with commas, and bignums) aren't important for many applications, which could just as easily use strtol from libc.

On x86-64:
IN: scratchpad \ base> word-code swap - .
34272

It's pretty inline-happy. It might be factored better to reduce code size—maybe it should do its own bignum checks and spill over to a separate bignum>base function so that it doesn't have to do a fixnum check at every operation.

Another thing that would help (suggested by @erg) would be to provide better factors of base> for string>integer or string>fixnum. Applications that only parse integers shouldn't drag around the float parsing code.

string>fixnum in particular could shake down a wrapper over strtol.

It's small enough for now.


Cog updatge

About the PR

added 2 new cameras to ai core (power room and entrance door)
redid ai core wiring and atmos
added happy honk vendor to kitchen backroom

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

You recolored distro to be... purple? Intentional?
Standard colors for atmos (including cog) are

Waste loop: #990000 (dull red)
Distro loop: #0055cc (subdued blue)

Other then that it looks good


Set restriction on the number of partitions in partition generator

[Short description explaining the high-level reason for the pull request]
Additions

Removals

Changes
src/partitionGenerator.cpp
Testing

Screenshots
Notes

Todos

Checklist

[x ] PR has an informative and human-readable title
[x ] Changes are limited to a single goal (no scope creep)
[x ] Code can be automatically merged (no conflicts)
[x ] Code follows project standards (link if applicable)
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Testing checklist (automated report can be put here)

Target Environment support

[ ] Linux

Generally some std::cerr output and a non-zero exit would probably be nicer than throwing a runtime exception, but I suppose this does the job.

Believe this fixes #456


HTTPS caching, self-signed SSL certificate, MITM

This is not a problem, just a comment.
HTTPS caching is possible if you set up the cache as a proxy server, create a self-signed SSL certificate, install the self-signed certificate on the cache server and the clients, and set the cache as the proxy for all traffic.
This allows the cache server to cache everything, HTTPS or not.
The downside is that the proxy cache can see all the raw HTTPS traffic accessed by clients, so it bypasses all security for any website using HTTPS accessed by the clients.
This is known as a man-in-the-middle security attack as the clients will explicitly trust the proxy cache due to the self-signed certificate and will not display any security warnings on the client devices.
Also without special filtering of certain SSL page content or URLs, it will end up caching things you do not want to cache, like the contents of shopping carts, bank account data, etc, so it can be challenging to make HTTPS proxy caching work properly.
Reference: https://stackoverflow.com/questions/14656/can-a-proxy-server-cache-ssl-gets-if-not-would-response-body-encryption-suffic

We are aware of this. Given our target market is LAN parties, i.e. people running events where other people that they may not know very well bring their own hardware, we don't wish to be encouraging everyone to break the chain the trust inherent in SSL. We feel that this would be irresponsible of the project, and is a big part of the reason why we lobby all the big distribution platforms to continue to support both HTTPS and HTTP.
As an aside, check out our SNI proxy repo which is our solution for MITM DNS for lancache without breaking HTTPS. https://github.com/lancachenet/sniproxy


Empty body shouldn't not show html5 warning

If a site just returns 401 or similar status codes, then of course it isn't valid html5. That Warning should only be shown if the content length is >0 and/or if it's html at all.
Alternatively, it could be checked what's the expected content type; for example verify it's valid json for application/json...
## HTTPS content scan results

Compression is not enabled
invalid html5: First non-comment node must be the doctype node, found html

HTML size: 0kB
Total download size (without media): 0kB

Fixed with next release, while the second part was added to upcoming feature list in README


Don't apply a language config to the output window

We applied a language setting to the output window's MIME type in order to colourise headers for output printed to that window (#28).  Unfortunately, this hijacks the language away from the VS Code Log 'language', resulting in the default linkifier not running on stuff in the output window.  This means that when, say, test runners output line references to the output window, those references cease to be linkified (#389).
Losing links in test runs is worse than having to grovel for command headers in k8s output, so let's remove the colourisation.

Fixes #389.


Added buttonOffColor props

I added option to have button color props when the button is not selected.

Hi.
Thank you for your PR.
But I think, we don't need add new props.
If you want to change color which not selected button, you can write this.
buttonOuterColor={IS_SELECTED  ? '#2196f3' : '#fafafa'}

I updated component to ver2.0.2 for this usage. And also I updated example.
Please check this:+1:

Thanks , it wasn't working on the previous version.

can you please tell me how can I make the selected label bold?
I need to bold the text of option which I selected


Transaction builder / signer DSL & Byron implementation

ChangeLog

7b4507142f739dd59761f7dc982ac58cd4f3ef3f
:round_pushpin: write simple DSL for transaction construction

3b8480d002432cd85f1c99ebb266608b4219f7d6
:round_pushpin: first draft implementation of Cardano Byron transactions

Comments
Still very drafty and lack of unit tests. But I've started grooming a bit the structure and it looks pretty nice so far.

@KtorZ  The abstraction works very ok for Byron, but are we sure it is going to accommodate what is coming for Shelley : https://github.com/input-output-hk/cardano-ledger-specs/blob/f1d5ddb25531b2512796d34e9cfd803f7af76567/shelley/chain-and-ledger/executable-spec/src/Shelley/Spec/Ledger/Tx.hs#L56


fix: server tests failing due to suggested widgets changes fixed

Description

This PR removes Text widget option from suggested widgets. We are removing this option as it has very low usage and usually connecting such huge data to text widget is irrelevant. More details can be found here
This PR also fixes JUnit test cases in ActionExecutionSolutionCETest, to ensure that removal of Text widget is reflected in the tests as well

PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Bug fix (non-breaking change which fixes an issue)

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] Jest
[ ] Cypress
[ ] JUnit

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test


Stop on MultiExiftool.Executable.parse_errors

I wrote a patch, then it works, but I do not known why.
module MultiExiftool
# Mixin for Reader and Writer.
module Executable
def parse_errors
if @stderr.stat.size.zero?
@errors = []
else
@errors = @stderr.read.lines(chomp: true).select {|l| l =~ /^(Error|Warning):/}
end
end
end
end

Strange. Which operation system do you use? Could you post a code example, which shows this behaviour?

I close this issue because I could not reproduce the problem. Feel free to reopen it if you have more information.

Maybe it's the same problem as #17

I hope it's fixed in multi_exiftool version 0.18.1. Let me know if it works for you.


After removing class, don't collapse the hierarchy

If you remove a class, it isn't helpful that the hierarchy collapses up to the parent class. Should show the hierarchy as it exists but without the removed class.

It behaves as the intended behavior as of v3.2.12, so this was fixed by some other work.


[Chat] Rerender ImageOverlay when selected image is fetched in the queue

What

Now that the full size images are fetched and cached in the stateful client layer, we want to listen to the update and re-render the ImageOverlay component when the image is fetched
This PR is to:

Fix the startQueue function to handle full-size image fetching
Add a new prop of fullSizeImageSrc to the InlineImageMetadata API
Update the MessageThreadSelector to read from the cache and add the fullSizeImageSrc to the ChatMessage
In ChatScreen, listen to the messages and update the state of ImageOverlay
Add keys to the inline image components
Remove the old downloadAttachment, AttachmentDownloadResult, and AzureCommunicationChatAdapterOptions
Fix tests

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Tested with no issues. Left a few comments. Will approve after they are resolved.


Define clearly somewhere how we're different from Elm

Personally, I feel like at first glance, Cycle.js seems to be Elm in plain JavaScript. I think we should have a section somewhere in the docs, or maybe just a link to a blog post somewhere, where we explain how the architecture of Cycle.js is different from that of Elm, why we may think that Cycle.js is a better concept than Elm (if we do think so) and what our main goals are.
Any thoughts? Modifications? Other ideas?

Watch this presentation http://www.atthefrontend.dk/session/Unidirectional-data-flow-architectures or read this blog post http://staltz.com/unidirectional-user-interface-architectures.html

Yes, I do know that. What I'm suggesting is linking to it in the docs.

Yeah we could put that in FAQ. For now, we can put it in the Wiki, and later we can move FAQ from Wiki to the docs site.


Adjusted playback speed for audio

Is your feature request related to a problem? Please describe.
When doing Sound Event Detection (SED) labeling in Label Studio, I find the included playback speed options to be insufficient. The lowest speed I can play the audio in is x0.5, which is much too fast for the precise time-boxing that SED requires.
Describe the solution you'd like
An expanded list of playback speeds with  or , so that precise labeling is more feasible. Preferably x0.25 and x0.1 playback speed.
Describe alternatives you've considered
For precise SED labels, there aren't really any good options I can think of.
Additional context
For SED labels to be somewhat precise, getting start- and end-time correctly within ~0.1s is sufficient. (At least for my application.)
Thanks!

Hey @Ludvig-Joborn 👋. Thanks for reaching out, I think this is easily workable to introduce this! I will generate a ticket and get this put into the backlog to be prioritized.

Thank you @bmartel! Please let me know when this feature goes live! :pray:


Remove double-space in defaults.json

Summary of the Pull Request
There was a double-space after a colon in defaults.json and defaults-universal.json.
PR Checklist

[ ] Closes #xxx
[x] CLA signed
[ ] Tests added/passed
[ ] Documentation updated
[ ] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan

Detailed Description of the Pull Request / Additional comments
It says at the top of these files that they are autogenerated, which made me wonder how they had a double-space.
Then I found this which says it is a lie and they're not autogenerated. Wat.
Validation Steps Performed

it is a lie and they're not autogenerated. Wat.

Yeah, so... that's a weird warning.


Coordinate Frames of Montage Converted from Unknown to Head Automatically?

Describe the bug
When I pass in a montage with `coord_frame = 'unknown'', and check the actual montage, it is all of a sudden in the head coordinate. I believe it is due to this line:
mne-python/mne/channels/montage.py:664

mnt_head = _get_montage_in_head(montage)

Inside function: mne.channels.montage._set_montage. As a result, raw.set_montage(montage) now has all coordinate frames in head frame.
Steps to reproduce
def _make_toy_raw(n_channels):
    return RawArray(
        data=np.empty([n_channels, 1]),
        info=create_info(
            ch_names=list(ascii_lowercase[:n_channels]),
            sfreq=1, ch_types='eeg'
        )
    )

  raw = _make_toy_raw(4)
    raw.set_channel_types({ch: 'ecog' for ch in raw.ch_names})
    ch_names = raw.ch_names
    n_channels = len(ch_names)
    ch_coords = np.arange(n_channels * 3).reshape(n_channels, 3)

    # create mne.DigMontage
    ch_pos = dict(zip(ch_names_raw, ch_locs))
    montage = mne.channels.make_dig_montage(ch_pos=ch_pos, coord_frame='unknown')
raw.set_montage(montage)

print(raw.info['dig'])

Expected results
A simple fix I presume would be to add a compute_head = True to the set_montage function, so that way you can turn it on or off?
Additional information
See: https://github.com/mne-tools/mne-bids/pull/390#discussion_r416942332 for related problems when trying to use mne-python to read/write data.

Actually for that matter, I'm also having a really hard time making the montages agree after set_montage and get_montage in this PR: https://github.com/mne-tools/mne-python/pull/7667
I believe the only change is this _get_montage_in_head() transformation that is applied.

I believe it is due to this line:
mne-python/mne/channels/montage.py:664

mnt_head = _get_montage_in_head(montage)

Inside function: mne.channels.montage._set_montage.

Hey @adam2392, this can make your life easier:
https://help.github.com/en/github/managing-your-work-on-github/creating-a-permanent-link-to-a-code-snippet
Also you can get syntax highlighting in code blocks if you start them with
"```python" :)

@larsoner we need to discuss this again.
chs loc "must" be in head according to MNE convention
but are we currently too strict with dig?

To me dig does not require all points in head coords, correct.
ch['loc'] we could in principle even relax because there is ch['coord_frame'], but it would require a lot of careful changes to get right (e.g., in forward calculation).

Hmm seems that the transformation would definitely impact EEG and MEG. Is it possible to at least as a simple fix, add a flag transform_head = True  or something to just allow iEEG data setting montage to get rid of this transformation?

To me dig does not require all points in head coords, correct.
ch['loc'] we could in principle even relax because there is
ch['coord_frame'], but it would require a lot of careful changes to get
right (e.g., in forward calculation).

i feel we should consider this as currenlty sEEG/ECoG folks will read in MRI
fake it head and than silently use trans Head<->MRI as Identity to get it
to work.
thoughts?

could we allow ch['loc'] to be not 'head' based on the channel type? Because there is no forward calculation to be done for ECoG data (yet) in MNE. Then you avoid complexity and only check this when setting.

i feel we should consider this as currenlty sEEG/ECoG folks will read in MRI fake it head and than silently use trans Head<->MRI as Identity to get it to work.

The question in my mind is, what should these people see for example with a topomap plot? Do we allow them to be silently in MRI coords when they do their plot? It breaks the uniformity of our topomap transformation, which might be worth it but we need to consider it.

Because there is no forward calculation to be done for ECoG data (yet) in MNE. Then you avoid complexity and only check this when setting.

If you're going to allow non-head for some sensor types (sEEG, ECoG), it's unclear why you wouldn't allow it in general, e.g., for EEG electrodes. Then you need to decide how to handle those cases in forward calculation (which IIRC is always done in head coords).
And unfortunately it's more than just the forward we need to consider. Any function that plots sensor locations or uses sensor locations needs to be checked that things are in the correct coordinate frame or that we aren't (still) implicitly assuming a head coordinate frame. So at a minimum the big things I foresee being problems are:

plot_alignment -- need to be more careful about coordinate frames (actually easiest to fix)
topomap -- do we allow non-head coords? do we use the same transformation we do for head? do will still draw a head outline?
forward -- do we allow computing in the MRI frame?
DigMontage -- do we still require fiducials and/or being in the head coordinate frame, or do we allow people to work with FIFFV_COORD_UNKNOWN for EEG?

If you're going to allow non-head for some sensor types (sEEG, ECoG), it's unclear why you wouldn't allow it in general, e.g., for EEG electrodes.

I am not an intracranial expert but I think it's not kosher in the sEEG/ECoG world to deal with a head space. You have a CT scan with the device coordinates and you transform them to MRI coordinates by aligning with the anatomical MRI so that everything is in MR coordinates.
I agree that supporting a full pipeline for ECoG is going to be challenging. I understood that we needed this only for MNE-BIDS to be able to help convert existing data to BIDS format @agramfort @adam2392 ?

You have a CT scan with the device coordinates and you transform them to MRI coordinates by aligning with the anatomical MRI so that everything is in MR coordinates.

Something similar can happen with EEG+fMRI, so I think we have to think more broadly than special-casing sEEG and ECoG

If you're going to allow non-head for some sensor types (sEEG, ECoG), it's unclear why you wouldn't allow it in general, e.g., for EEG electrodes.

I am not an intracranial expert but I think it's not kosher in the sEEG/ECoG world to deal with a head space. You have a CT scan with the device coordinates and you transform them to MRI coordinates by aligning with the anatomical MRI so that everything is in MR coordinates.
I agree that supporting a full pipeline for ECoG is going to be challenging. I understood that we needed this only for MNE-BIDS to be able to help convert existing data to BIDS format @agramfort @adam2392 ?

Idk what a full pipeline would look like for ECoG/SEEG in mne, but honestly, I'm okay with just coordinate frame support when set_montage is called. Transforming to head seems weird to me. Just having a unified data structure that doesn't get arbitrarily modified/transformed would be a good start. E.g. you create a digMontage from coordinates and you know its in a specific T1 MRI coordinate system, then I think your downstream analysis can happen outside of  mne (for now?)
Because of that, to maintain backwards compatibility, why can't we just add a transform_to_head=True parameter to set_montage? This then lets iEEG users just turn it off and stick w/ the mne supported "ras", "mri", "mri_voxel", "fs_tal", "mni_tal" coord systems. If iEEG users want to use the above supported pipelines to do some visualizations, just document that currently you need to "transform_to_head"?

I think we have addressed this in MNE-BIDS and MNE-Python but @adam2392 feel free to reopen if I'm mistaken


Refactor ParseMessage() method

controller/response.go:27::warning: cyclomatic complexity 21 of function ParseMessage() is high (> 10) (gocyclo)

Cyclomatic is now 13, pretty ok for now. Thanks!


Feature/alg 287 refactor ssd

Refactoring SSD to be based on CustomizableDetector. Many lines changed due to Black. Real changes are:

Split SSD into backbone, neck and head, now all these modules can be replaced/reused with other backbones/necks/heads from the detection modules factory with minimum understanding of the required yaml structure;
Moved customizable backbone, neck and head into a different location due to circular imports, other than migration this code didn't change;
Add variable input_channels to MobileNetV1
Fix inference of MobilenetV2 in backbone mode
Minor change in MultiOutputModule to support lists from yamls (ListConfig isn't an instance of list);
Fix head replacement in customizable detector;
In pretrained models test the only real change is this line:

ssd_dboxes = DEFAULT_SSD_LITE_MOBILENET_V2_ARCH_PARAMS["heads"]["SSDHead"]["anchors"]

updated pretrained weights in S3 (by the same path as before) to match the new state dict, ran the test

Black forced me to re-save these files, no real changes there:
would reformat src/super_gradients/examples/deci_platform_logger_example/deci_platform_logger_example.py
would reformat src/super_gradients/common/sg_loggers/deci_platform_sg_logger.py
would reformat src/super_gradients/sanity_check/env_sanity_check.py
would reformat src/super_gradients/training/utils/quantization_utils.py