18:06:47 <selsta> .merges
18:06:47 -xmr-pr- 9130 9136
18:52:23 <m-relay> <j​effro256:monero.social> Would someone who knows anything about the serialization code be able to take a quick peek and review this PR: https://github.com/monero-project/monero/pull/8940/files. It simply adds a unit test case which confirms a property about the serialization of empty arrays
19:18:09 <m-relay> <j​effro256:monero.social> Alex | LocalMonero | AgoraDesk: I just think that it was the most straight forward way to code it
19:20:29 <m-relay> <a​lex:agoradesk.com> The default wallet behavior should probably be to flush cache changes to storage, just like it is in other wallets. Due to the lack of automatic flushing, if there's a wallet running on a system for some time and the system or wallet crashes then there needs to be a lot of unnecessary resyncing. This puts unneeded strain on both the user and the network.
19:28:37 <m-relay> <p​lowsof:matrix.org> competent devs notice this and use the store rpc command at an interval of their liking (just like they are aware of the unlock_time value)
19:55:12 <m-relay> <a​lex:agoradesk.com> Unlike timelocks, which are abundant in crypto, it's not normal for wallets not to flush cache.
21:25:00 <ofrnxmr> (Rpc calls auto_refresh automatically on intervals. Is there any reason to not (auto) save the wallet during the refresh interval?)