02:41:33 <m-relay> <g​ingeropolous:monero.social> syncing release on a 7400 spinny. 97.6% there, up 1d16hrs straight.
02:41:55 <m-relay> <g​ingeropolous:monero.social> release-v0.18 , not gitian
02:52:22 <plowsof> 11 hours in with gitian 49% 
14:07:06 <m-relay> <w​oodser:monero.social> unrelated to the upcoming release, but I've been seeing a longstanding issue where if importing multisig info fails the first time (e.g. no connection to daemon), then it succeeds the second time, then it'll cause an error when signing a multisig tx: `-35: Failed to sign multisig tx: This signature was made with stale data: export fresh multisig data, which other participants must then use`
14:07:21 <m-relay> <w​oodser:monero.social> so in that case I have to create the multisig tx anew, and then have the original peer complete the signing
14:07:32 <m-relay> <w​oodser:monero.social> any idea what could cause this "stale data" error if `import_multisig_info` is called twice because the first request fails? seems to be a bug of some kind
14:33:29 <m-relay> <w​oodser:monero.social> in case @jberman or vtnerd might have any ideas :)
20:55:22 <m-relay> <g​ingeropolous:monero.social> 7400rpm finished sync. no issues, full up