selsta Are you in charge of the new RISV 64-bit CI build ?

jberman: is background-sync code production ready? thinking about adding it to my wallet

I'll have it there by end of this week. Was just about to move back over to it

r4v3r23: IIRC the biggest thing it still needs is a check that it's enabled in commands that require usage of the spend key, so they error out and indicate the user should disable the mode. Like CHECK_MULTISIG_ENABLED

jberman[m]: excellent, i was about to start work on the wallet sync part so this is perfect timing

nice :)

<jberman[m]> "r4v3r23: IIRC the biggest..." <- not sure i follow here, when background sync is enabled user will have to disable it to use spend functions?

as implemented, when background sync is enabled, the spend key is wiped from memory. the spend key needs to be brought back into memory to be used (which requires the user to re-input their password). I implemented `disable_background_sync_mode` to accept the password as input and load the spend key:

better link: github.com/j-berman/monero/blob/238…b0fd5/src/wallet/wallet2.cpp#L13189

right, ok that makes sense

jeffro256[m]: not sure what you mean with in charge

I added it to CI because there was an example for it in our README but otherwise I don't know much about RISC-V

i have been asked to approach a community work group (dev) to review my investigations at github.com/plowsof/verify-mb-gui-binaries

selsta do you know why the ccache job would loop for 6 hours before being canceled?

link?

Is it downloading something?

THe only messages are "Received x of 104621227 (y%), 0.0 MBs/sec"

can you reproduce this? or did it only happen once?

seems to be a github cache action bug

never seem this before