04:14:52 <emrwoiiyd> “I thought, ‘I’m going to pump it and dump it,’ because I was interested and taking the ideas and implementing them in bitcoin. The bitcoin code base was far more interesting to me than monero, and I thought, ‘I’m not going to work on this codebase, it’s terrible,'” he recalls - fluffypony in an interview about Monero
06:59:43 <mj-xmr> selsta, I have updated the documentation in 7387 and ran the Mac test. Unless you have nothing to add after your own Mac test, we're done on this one.
07:00:13 <mj-xmr> BBL. Lovely SCRUM meetings ahead.
10:08:25 <luigi1111> froglet_xmr: try your question again
10:23:04 <froglet_xmr> ack, luigi. hi folks, I am attempting to receive XMR on stagenet (connected to a remote node), the TX briefly shows up in monero wallet gui but then disappears. I can see from a blockchain explorer that the TX has been confirmed several times, but still no luck in seeing it in the GUI. any advice?
10:23:40 <selsta> is your gui set to stagenet?
10:23:45 <froglet_xmr> yes
10:23:56 <froglet_xmr> I see stagenet in red text in the top left corner
10:24:16 <selsta> ok
10:24:36 <selsta> which stagenet node are you using?
10:26:27 <froglet_xmr> I have tried both monero-stagenet.exan.tech and the xmr.to node (full address escapes me at the moment..)
10:27:13 <froglet_xmr> stagenet.community.xmr.to
10:27:45 <froglet_xmr> currently i am on exan.tech node, synchronized (792543)
10:28:10 <froglet_xmr> port 38081
10:28:34 <selsta> would try the xmr.to one
10:29:02 <froglet_xmr> I get the same result
10:29:42 <selsta> is your balance correct?
10:30:28 <froglet_xmr> well, my balance is 0 XMR which would be correct if I have never received any XMR on stagenet (wallet was only created today)
10:30:51 <froglet_xmr> however it would be incorrect if the faucet transactions have in fact been sent to me
10:31:37 <luigi1111> briefly shows up then disappears seems weird
10:31:42 <froglet_xmr> eg. https://community.xmr.to/explorer/stagenet/tx/545b7c65e65532911062cb2b4cb186ad3156a2d0c5049bebe036387c9b70dc6f should have been sent to my wallet on stagenet
10:32:31 <froglet_xmr> everything I see about the tx seems to suggest that it has been confirmed, several times, but my wallet still shows 0 XMR
10:32:45 <selsta> can you try CLI wallet?
10:33:05 <froglet_xmr> i'm not familiar with using the CLI but yes I can try..
10:33:14 <froglet_xmr> CLI wallet I should say
10:34:03 <selsta> did you change account inside GUI?
10:36:53 <froglet_xmr> changed wallets, yes
10:37:02 <froglet_xmr> created a new one on stagenet, i have a working wallet on mainnet
10:39:03 <selsta> ok but you did not change anything on the "Accounts" tab
10:39:56 <froglet_xmr> correct
10:40:27 <froglet_xmr> i created a new receive address though, to verify it wasn't something wrong with my main address
10:41:32 <froglet_xmr> using the wallet-cli (assuming I have done so correctly) still shows a balance of 0 XMR
10:41:54 <froglet_xmr> however I do get a message saying "The wallet's refresh-from-block-height setting is higher than the daemon's height: this may mean your wallet will skip over transactions"
10:44:08 <froglet_xmr> I ran "wallet_info" from the CLI and now it says my wallet is out of sync
10:45:11 <selsta> ok so the restore height is the problem
10:46:36 <selsta> you can enter "set refresh-from-blockheight 792400"
10:46:51 <selsta> and then enter rescan_bc
10:47:03 <froglet_xmr> i checked that, restore height is 2317388, is it possible there is some bug where creating a wallet from the gui would use the mainnet restore height perhaps..?
10:47:40 <froglet_xmr> I get Error: set: unrecognized argument(s) from that command selsta
10:48:10 <selsta> set refresh-from-block-height 792400
10:48:12 <selsta> does that work?
10:48:39 <froglet_xmr> yes it did
10:48:46 <selsta> could be a GUI bug during stagenet wallet creation, though did not see it before
10:49:09 <froglet_xmr> i am running a mainnet local node, maybe that has something to do with it
10:49:28 <froglet_xmr> alright that worked! thanks so much for that, i was really scratching my head..
10:49:49 <froglet_xmr> makes sense, so the laymans explanation is that my wallet thought it was from the future...
10:53:19 <selsta> yep
10:53:29 <selsta> it had the mainnet restore height
10:54:56 <froglet_xmr> very strange that the TX would also appear in the GUI at 0/10 confirmations and then disappear after a while
10:57:21 <selsta> I assume it saw it in the mempool but then skipped it
10:57:37 <selsta> after it got in a block
11:04:28 <tqhqfjrcbrgb> I think everyone here knows that most Monero exchange withdrawals and desposits are traceable (Breaking Monero - poisoned outputs). How does it feel to go out and lie to people that they are private and then earn less than holding BTC on your bag?
13:41:30 <agentpatience> Did you know one of the developers is working on integrating Triptych?!
13:41:30 <agentpatience> Triptych is a zero-knowledge proving system for confidential transactions created by the Monero Research Lab!
13:48:36 <moneromooo> Please don't spam.
14:00:55 <childofthecorn[m> Please 🙏
17:24:46 <selsta> .merges
17:24:46 -xmr-pr- 6810 7005 7274 7332 7349 7366 7368 7373 7394 7398 7400 7401 7402 7412 7413 7417 7418 7419 7422
18:00:07 <mj-xmr> It's a good review, after which I facepalm after realizing that I'd unintentionally introduce a security breach.
18:00:08 <mj-xmr> https://github.com/monero-project/monero/pull/7469
18:00:18 <mj-xmr> (core_tests)
18:38:51 <ndorf> just in case people are unaware, github has a setting under which " Users that have recently created their account will be unable to interact with the repository," which also automatically expires after a specified length of time.
18:43:50 <selsta> fluffypony: opinion? ^
18:44:39 <mj-xmr> Unrelated: does MTRACE create a backtrace?
18:45:02 <selsta> sounds like the trace log level
18:47:52 <moneromooo> MTRACE logs at trace level. For a trace, use: tools::log_stack_trace();
18:48:22 <mj-xmr> Thank y'all.
18:53:58 <ebebopasnj> All you are 'fighting' for is e-penis of a guy you never met, that doesn't even have common decency to pay you for your time.
18:53:58 <ebebopasnj> Do you think they care about Monero, or privacy or anything other than money?
18:57:55 <dEBRUYNE> selsta: I'd enable that, it would curb the spam and perhaps occasionally catch a false positive
19:01:43 <selsta> yea, would set it to 1 week for now
19:13:27 <mj-xmr> I need stack trace in epee, but stack trace's common depends on epee. I have to decouple logging from epee.
19:18:14 <mj-xmr> I would like to help the guy with the log spam before I make these changes. What I could offer ad-hoc is compressing the rotated logs with XZ. If they contain spam, then the 100 MB log will reduce into 1-2 MB after compressing.
19:18:14 <mj-xmr> https://github.com/monero-project/monero/issues/7539
19:18:53 <selsta> mj-xmr: it's seems to be a gui issue
19:19:09 <mj-xmr> yep
19:19:49 <selsta> not showing up with start-low-graphics-mode.bat usually hints at a graphics drivers issue
19:20:00 <selsta> not clear how graphics driver is related
19:20:08 <mj-xmr> But I feel somehow blind, not being able to trace the cause (or any other in epee without proper logging).
19:22:03 <mj-xmr> I think I will just do what I can do best and decouple logging from epee, similarly as epee_readline is decoupled.
19:24:14 <mj-xmr> Does compressing the rotated log sound like something you'd want to see regardless of the final solution?
19:26:15 <moneromooo> Then: try { throw 0; } catch(...) {}
19:26:36 <selsta> seeing that it only shows up at a single user and that graphics drivers seem to be related here I don't know if it's worth to spend much time on
19:26:55 <selsta> usual solution is attempt to update drivers and check if issue reappears
19:26:56 <moneromooo> You mean adding log compression to monero tools themselves ?
19:27:21 <mj-xmr> moneromooo, yes.
19:29:17 <mj-xmr> So there is already log rotation. Compressing the rotated logs seems like the natural next step.
19:29:34 <selsta> does that work without extra library?
19:29:52 <mj-xmr> Boost has compression routines.
19:30:20 <mj-xmr> If you're happy with zip and gzip, you shouldn't need anything more.
19:31:14 <selsta> I guess it can be useful when running log level 4
19:36:18 <selsta> mj-xmr: mining test also passed on my mac
19:36:38 <selsta> p2p functional tests fail somehow but seems unrelated
19:36:39 <mj-xmr> excellent!
19:49:34 <mj-xmr> selsta, if p2p was never being tested under Mac, one can expect such failures.
19:49:46 <mj-xmr> But it sure is something to add to the list.
19:50:02 <selsta> it worked in the past
19:51:45 <mj-xmr> I can imagine this. But if it's mot in the CI, a regression can happen anytime.
19:52:35 <mj-xmr> But to remove my bias, I could run the full test on GitHub on Mac on Master.
19:55:28 <mj-xmr> Shall I?
19:56:08 <selsta> didn’t you run functional tests yesterday?
19:56:18 <selsta> or did you only run mining test
20:02:17 <mj-xmr> Only the mining test.
20:02:38 <mj-xmr> Because I have modified the functional_tests_rpc to just run the "mining" test, not "all"
20:03:06 <mj-xmr> Otherwise I'd spam the logs.