04:36:40 GUI bug that I might submit later to github but am leaving here in case I forget 04:37:35 If you try to send an amount that exceeds the existing balance from account A, and then switch to account B (with sufficient funds), the 'amount exceeds unlocked balance' warning (and locked send button) persist until the amount is modified 04:37:53 Switching to the Send tab should cause a refresh 06:09:01 dEBRUYNE: yes the spend proof just requires your private address keys; it sounds like the reddit guy wants to make an OutProof, which is only possible with the tx private key 06:47:30 moneromooo: is there a way for miners to manipulate the "already_generated_coins" amount when contracting miner tx in "construct_miner_tx"? 06:48:33 *constructing 06:51:06 and is already_generated_coins the total coins minted after or before the mined block 06:54:34 in blockchain.h, one comment says already_generated_coins is "the total coins minted after that block" and while another one says "the amount of currency generated prior to this block" 08:00:32 -xmr-pr- jiebanghan opened issue #6749: CMake Error: Could not create named generator MSYS Makefiles 08:00:32 -xmr-pr- > https://github.com/monero-project/monero/issues/6749 09:15:32 -xmr-pr- Adreik opened issue #6750: Wallet that did not generate transaction cannot store private transact... 09:15:32 -xmr-pr- > https://github.com/monero-project/monero/issues/6750 10:09:07 You can pass an override to the function, and use that if set. 10:09:33 Presumably before the block is mined. I would have to see hte code to make sure. 10:09:51 But it increases after each block, so both are technically true :) 10:48:47 Hi 12:05:33 CLI v0.16.0.3 binaries are up on getmonero.org. Thanks a lot to everyone contributing their build hashes, and selsta in particular for driving this 12:05:46 And all contributors etc of course :) 13:50:33 Awesome, all nodes migrated to 16.0.3 without flaw :) 14:12:22 what are key new stuff? 14:12:37 DoS fixes and other bug fixes/minor changes 16:00:32 -xmr-pr- hrodrig opened issue #6751: Fresh monerod in macOS update silent fail: what's mean "bus error" ? 16:00:32 -xmr-pr- > https://github.com/monero-project/monero/issues/6751 21:19:09 hello 21:19:58 hey; moneromooo, that patched wallet your sent yesterday, where does it put the logs? 21:30:44 monero-wallet-cli.log, same directory as the binary. 21:50:21 And does he need to run it at a specific log-level? 21:50:37 yes, --log-level 0 23:13:42 moneromooo: can you take a look at https://github.com/monero-project/supercop/pull/4 ? 23:16:27 done 23:17:27 okay luigi1111 please also merge ^ later when you do merges 23:17:48 https://usercontent.irccloud-cdn.com/file/tU7w1vqo/monero-wallet-cli%20(1).log 23:18:07 moneromooo - here is the log from the affected user 23:22:50 KnifeOfPi: from which height did they restore? 23:23:55 It does not have my patch. 23:24:56 It also logs extraneous stuff. Looks like it's not other changes in. 23:25:35 And if it is the case, I'm not going to debug further :) 23:25:52 it's got* 23:26:32 That patch didn't apply here. 23:26:37 https://github.com/selsta/monero/commits/cake 23:26:38 The second one. 23:26:55 that’s the branch I compiled 23:27:25 That seems right. 23:27:46 KnifeOfPi: can you double check if they selected the correct monero-wallet-cli ? 23:27:54 yes 23:28:13 iDunk: can you check if this one has the patch applied? https://gui.xmr.pm/files/cli/cake-issue-tmp/ 23:29:16 he claims he used the right one 23:30:28 I guess you can run strings on it and grep for "process_new_transaction" 23:30:58 Or upload it to some file sharing host and I will. 23:31:38 it does have process_new_transaction in it 23:31:54 so the binary is 100% correct 23:31:59 Maybe he sent the wrong log then. 23:32:26 For example: ERROR wallet.wallet2 src/wallet/wallet2.cpp:2501 start_height=2166876,curre 23:32:38 2105 just has "else" in selsta's branch. 23:32:56 2501 23:34:08 yep, definitely wrong log or wrong .exe selected 23:37:01 https://usercontent.irccloud-cdn.com/file/jMVFXVPA/IMAGE%202020-08-07%2019%3A36%3A57.jpg 23:37:05 here is screenshot from the user 23:39:54 KnifeOfPi: the log you sent is 73kb, the one on the screenshot 103kb 23:40:09 huh... i'll ask him again 23:51:20 he is insisting it's shrinking after he sends the log... 23:52:47 Makes sense, since it's removing my new logs and inserting those unknown logs instead. 23:55:10 That said, it could technically be true, windows inserts extra \r characters on newlines. 73/103 seems way too much though. 23:56:48 I will test that branch now and look if the logs look like expected