--- Log opened Tue Feb 15 00:00:59 2022
00:40 -!- rusty [~rusty@203.221.55.113] has joined #c-lightning
01:10 -!- rusty [~rusty@203.221.55.113] has quit [Ping timeout: 252 seconds]
01:56 < nixbitcoindev[m]> What happens to SQLITE3 native replication (due for 0.10.3) when the remote host goes down mid-write?
01:58 < vincenzopalazzo> nixbitcoindev: i assume that the transaction is reverted? not an expert of sql, but I'm assuming that the replicatiton will be a CRUD operation
02:04 -!- kexkey [~kexkey@static-198-54-132-86.cust.tzulo.com] has quit [Ping timeout: 256 seconds]
02:06 -!- kexkey [~kexkey@static-198-54-132-134.cust.tzulo.com] has joined #c-lightning
02:22 < cdecker[m]> There is no "remote" when working with sqlite, it's all locally mounted disks. So if you have a remote disk mounted locally, and the remote host disconnects or the connection is interrupted, then the FS subsystem will likely hang for a bit while it's trying to reconnect, but eventually it'll return an IO error, which sqlite3 treats as fatal and we will stop (with what looks like a crash, we're good at freaking people out that way...).
02:22 < cdecker[m]> This is the only safe thing to do at this point, since going on without replication can result in loss of funds.
02:34 < nixbitcoindev[m]> Ah OK, but there will be no loss of funds in that a transaction is performed but not written to the database?
02:39 < cdecker[m]> Correct, we're very careful about writing to local storage in a persistent manner, including backups and sqlite3 replication, before sending out anything that could be dangerous. This means that the on-disk storage is either equal to the protocol state, or one step ahead, but never lagging behind, which is the risky state.
02:40 < nixbitcoindev[m]> Amazing, thank you! Our implementation of the built-in replication + SSHFS + gocryptfs is almost ready to merge, when do you think 0.10.3 will land?
02:56 < cdecker[m]> Soon (TM), we have some killer features we want to land with this version, which aren't quite ready yet :-)
03:02 -!- jarthur [~jarthur@2603-8080-1540-002d-b815-d0c3-2814-01b3.res6.spectrum.com] has quit [Quit: jarthur]
04:24 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning
04:52 -!- jonatack [jonatack@user/jonatack] has quit [Quit: Connection closed]
05:14 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:33 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning
06:02 -!- kabaum [~kabaum@193.138.218.212] has joined #c-lightning
06:28 -!- jonatack [jonatack@user/jonatack] has quit [Ping timeout: 252 seconds]
10:31 -!- rusty [~rusty@203.221.55.113] has joined #c-lightning
11:03 -!- sr_gi [~sr_gi@47.61.62.163] has quit [Read error: Connection reset by peer]
11:03 -!- sr_gi [~sr_gi@47.61.62.163] has joined #c-lightning
12:18 -!- jonatack [jonatack@user/jonatack] has joined #c-lightning
12:21 -!- rusty [~rusty@203.221.55.113] has quit [Ping timeout: 240 seconds]
12:58 -!- jarthur [~jarthur@2603-8080-1540-002d-596e-b8a7-f58c-1fa5.res6.spectrum.com] has joined #c-lightning
14:24 -!- kexkey [~kexkey@static-198-54-132-134.cust.tzulo.com] has quit [Quit: kexkey]
14:36 -!- Guest87 [~Guest87@c-71-228-67-230.hsd1.fl.comcast.net] has joined #c-lightning
14:36 < Guest87> How can I close a channel with a peer that has a wire error every time I try to connect?
14:36 < Guest87> logs:
14:36 < Guest87> "Peer has reconnected, state AWAITING_UNILATERAL"
14:36 < Guest87> "peer_out WIRE_ERROR"
14:36 < Guest87> "disconnected"
14:45 -!- rusty [~rusty@pa49-178-141-153.pa.nsw.optusnet.com.au] has joined #c-lightning
14:51 -!- rusty [~rusty@pa49-178-141-153.pa.nsw.optusnet.com.au] has quit [Read error: Connection reset by peer]
15:06 -!- Guest87 [~Guest87@c-71-228-67-230.hsd1.fl.comcast.net] has quit [Quit: Client closed]
15:21 -!- Netsplit *.net <-> *.split quits: dergoegge, sturles, waxwing, grubman
15:23 -!- Netsplit over, joins: waxwing, dergoegge, grubman, sturles
15:30 -!- rusty [~rusty@203.221.41.134] has joined #c-lightning
18:19 -!- Guest87 [~Guest87@c-71-228-67-230.hsd1.fl.comcast.net] has joined #c-lightning
18:41 -!- kexkey [~kexkey@static-198-54-132-118.cust.tzulo.com] has joined #c-lightning
20:34 -!- rusty [~rusty@203.221.41.134] has quit [Ping timeout: 252 seconds]
21:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
21:07 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
22:08 -!- kexkey [~kexkey@static-198-54-132-118.cust.tzulo.com] has quit [Ping timeout: 240 seconds]
22:09 -!- opsec_x122 [~opsec_x12@44-25-143-42.ip.hamwan.net] has joined #c-lightning
22:10 -!- kexkey [~kexkey@static-198-54-132-118.cust.tzulo.com] has joined #c-lightning
22:11 -!- Guest87 [~Guest87@c-71-228-67-230.hsd1.fl.comcast.net] has quit [Quit: Client closed]
22:11 -!- opsec_x12 [~opsec_x12@44-25-143-42.ip.hamwan.net] has quit [Ping timeout: 240 seconds]
22:19 -!- Bikram [~Bikram@103.220.88.193] has joined #c-lightning
22:43 -!- Bikram [~Bikram@103.220.88.193] has quit [Quit: Client closed]
22:43 -!- jarthur [~jarthur@2603-8080-1540-002d-596e-b8a7-f58c-1fa5.res6.spectrum.com] has quit [Quit: jarthur]
--- Log closed Wed Feb 16 00:00:00 2022