09:12:33 is there a blockchain.raw for stagenet? 09:12:59 is there a regular pruned blockchain.raw anywhere? 09:37:16 No and no as far as I know 09:37:18 ^ azy 19:00:35 hi 19:01:07 im redesigning the progress bars in monero gui 19:02:05 I see that sometimes the blocksToSync can be different from targetBlock - currentBlock 19:02:22 is it common? 19:03:05 can the difference be large enough? 19:04:10 Im asking this because I'd like to leave the 100% width of the progress bar as just targetBlock - currentBlock 19:08:37 rating89us-: there is also #monero-gui 19:09:25 not sure where you should post as I am just a clueless person 19:09:43 truth not troll 19:14:11 If targetBlock refers to target height from the daemon, that's a sync mode value. If not in sync node, it's not used. I don't know if it refers to it or not, I just note it has a similar name so it might. 19:16:51 nevermind i found a solution, thanks 19:32:28 rating89us: Could be that we work accidentally on the very same thing right now :) 19:32:51 I finally came around to implement this here, from January: https://github.com/monero-project/monero-gui/issues/2713 19:33:17 Commit on my own repo is here, no PR yet: https://github.com/rbrunner7/monero-core/commit/2f5095e4dc80aa7ebd650d283a437b97da5876f9 19:34:44 Do we indeed conflict here? 19:35:11 AFAIK rating89us- is working more on design changes. 19:35:32 rbrunner: your change looks pretty simple and can get merged quickly, design changes will take more time 19:36:45 Thanks for the info. Let's see whether rating89us comes back to comment as well ... 19:37:34 I was indeed surprised how easy my proposal was to implement. In hindsight should have done that a long time ago 19:38:09 fwiw QML is quite easy to get into 19:38:40 Yeah, and the logic with the different 100% for the progress bar really was not that hard 19:39:20 And it turned out the control is also quite forgiving all on itself. Feeding it -50 and 200 did not result in anything bad :) 19:39:33 (The Qt control itself) 19:44:53 I'm doing some changes to both daemon and wallet bar 19:45:25 adding the height mark in both progress bars 19:46:35 i'll open a pr to show it better 19:46:46 ops, issue 19:48:35 Alright, will have a look tomorrow to check how it compares with my changes. 19:48:59 ok, i'm almost finishing it 19:49:04 i guess tomorrow it will be ready 19:50:21 Funny how nothing changes with those bars for months and then 2 people get to work at the same time :) 21:48:51 woodser: did you bisect that block weight test fail yet ? 21:49:45 no I've been focused on the issue with only account 0 info returning 21:49:57 was wondering if you posted another patch for that while I was disconnected? 21:50:26 I posted another based on master, not sure whether yo uwere disconnected at the time. Let me find it... 21:50:57 excellent I was disconnected 21:51:02 https://paste.debian.net/hidden/083e8332/ 21:51:06 But you said: < woodser_> got it, thanks 21:51:20 So I guess this one ain't good either ? 21:51:22 your first patch was not based on master, if I recall. didn't get a second 21:52:22 Can you pretend this one is maybe based off master and try it ? :) 21:52:57 yes 21:52:57 Or maybe I posted the wrong URL, lemme check quick... 21:53:14 the patch I tested resulted in an out of memory access 21:53:15 trying this one 21:53:39 Ah. Either you had not mentioned this, or I missed it. 21:53:57 What do you do which I could do here to see if it works ? 21:54:53 all I do is open a wallet that has balances in multiple accounts, and call balance_all (there are other methods too), and it returns only account 0 balance 21:56:21 Alright, manual, then I'll do that sometime later. 21:57:24 yeah this is the same patch as yesterday which accessed memory out of bounds 21:58:28 it can also be observed through monero-wallet-rpc, e.g. get_balance