Thx iDunk, it works using debug-static-all target.

I've a bug when trying to do a transfer (CLSAG, PR #6739), my password doesn't work anymore when it's asked again:

(Obviously this is the same one used when I start monero-wallet-cli)

grydz: what commit are you on?

we reverted 1 commit, try to git fetch

selsta: since he's checked out a pull request, will he not have to rebase it too?

or revert it himself

yes

hmmmmmm getting a "Error: internal error: Transaction sanity check failed" on a transfer

that's a new one

fluffypony: afaik temporary workaround is sending smaller amount

yeah smaller amount seems to work

xiphon: do you know about this ^ ? afaik you added some retry code

selsta, commit 8a9214e

grydz: rebase with master

Thanks, it works. I'm back to my initial untrusted secret problem which should only be related to the device part (gist.github.com/grydz/dc76dae3fee6fb3d20d519a01c355318) :D

So close, eh?

Hmmm I hope so :P

not a big deal, but just curious in case someone happens to have an idea: does the monero blockchain have much of an impact on SSD performance degradation?

hyyc said he wore a microsd out running a full node, after 2 years i think

ah, okay! Thanks... that's exactly what I was concerned about, especially since it's an internal (not practical to replace) drive. It was becoming a bit of a hassle keeping the database on an external drive, but seems worth the piece of mind

im not sure how much a microsd compares to an ssd though, ive never heard of anything other than that one microsd comment

Meeting in #monero-research-lab begins at 17:00 UTC (about 10 minutes from now)

Should we set a fork height for the network upgrade?

I would never use non-removable internal storage for the blockchain

whether microSD or SSD or whatever

now that we also store the txpool in the DB, the I/O load can get pretty intense, it will certainly wear out any device in a few years

s/fork height/block height

the only way to prevent such wear is if the device capacity is several times larger than the DB

<ErCiccione[m] "Should we set a fork height for "> Probably would be a good idea

Lots to do on the checklist (if we're using that)

We should use that :)

that's the point

ErCiccione[m]: Don't we usually set one right before the tag

iirc it is typically one of the last pull requests

Yeah we should definitely use it, now and in the future

dEBRUYNE: I might be misremembering, but i thought the last time we kinda said "should we set it?" and we did. I hoped to spark the same reaction :P