03:09:30 Hi guys, anyone build succeed in solaris? 03:10:04 There were errors about in6addr_any undeclared issues 03:10:22 Does anyone meet this before? 10:40:49 can a monero transaction co-exist in mempool and blocks with same tx_hash? 10:49:02 nandubatchu: In src/cryptonote_core/cryptonote_core.cpp in core::add_new_tx, the transaction is not actually added to the mempool if the mempool or blockchain already has it, so I guess not 11:58:44 BLOCK ADDED AS ALTERNATIVE ON HEIGHT: what does this mean? 12:08:22 netsplit? 12:08:32 feels like the 90s again 12:15:33 I am seeing two transfers inside a wallet one of type "in" and other of type "pool" with the same tx_hash. 12:15:42 Is this an expected behaviour? 12:15:50 Where do I post this question? 12:17:37 here, but you may want to stick around a little for a good answer :) 12:26:08 anyone have some xmrs to give me? 12:26:24 i'm in stagenet, all faucets seems to be not working 12:27:06 maxwilliamson, https://community.xmr.to/faucet/testnet/ 12:27:25 says "Sorry you are blocked." 12:27:29 also you can easily mine it with the node solo mode 12:27:40 use tor ? or a vpn ? 12:27:47 give me your stagenet address 12:27:49 nah, normal conn 12:27:56 address 12:28:01 It used to build pm Solaris. Patches welcome if it doesn't anymore. 12:28:08 53rrTSdMTD8a84afiUuc79GUGTXH3kaaGgJiAAnT5SbFdBEenToJjSg2KBmPB8nZPC9qXXCZoLnPLZzAujyB5RNoFUvaEiU 12:28:15 stagenet ? 12:28:45 hmm faucet seems not to be working tho ... 12:28:53 yeah stagenet 12:29:08 you runing a node ? 12:29:13 yep 12:29:17 just set mining on wait a while 12:29:45 maxwilliamson: I can send you also stagenet coins? 12:30:02 i_a_ would appreciate that 12:30:07 ok just a second 12:31:15 tomsmeding: any lead to ask this question to? 12:31:24 moneromooo: any help on my issue? 12:31:54 * moneromooo looks back 12:32:10 Ah, I missed it. Fixed in git. 12:32:46 maxwilliamson: txid 1583fb874c8a52de70c15e47155a759a57607354e054e31e777ce1f2095d51bf (still in a pool) 12:32:49 And on master: 27457a2 12:33:38 checked, thx man you're a lifesaver. 13:13:13 moneromooo: actually all the incoming transfers are duplicated with type="pool". 13:15:56 Evem with the patch ? 13:18:05 moneromooo: which patch? 13:19:02 The one I just pointed you to above. 16:59:51 stupid question: i have a couple transactions in mempool on my node. some 4 hours old. they show as relayed: true but are not mined. what are the possible reasons? 17:00:20 also I can't find them neither on xmrchain nor on node.supportxmr.com 17:20:57 can I re-relay the TX? 17:23:18 I have nothing in my txpool older than 2 minutes 17:25:38 Could be they're invalid. Could be you had a network hiccup at the time, and they did not get re-relayed yet. 17:25:51 Could be you're connected to only evil nodes that drop your data. 17:26:30 Could be you're lying, or can't read. Could be I'm misreading your stuff. Or some MITM changed your line in flight. Or I'm imagining all of this... 17:28:13 moneromooo: well, I'm not lying, so we can rule that out. trust me :P 17:30:29 all I know is I have 29 pool payments jacked up in mempool, monerod is happily syncing and the tx are marked as relayed. 17:30:53 It's your own txes then ? 17:31:01 Greating a completely useless error attempting to re-relay them. I'm going to pull the monerod logs in a sec. 17:31:22 Did you double spend them from another daemon right after ? 17:33:29 Oh, if you set_log +*txpool*:DEBUG then start_mining then stop_mining, it'll tell you why it doesn't add them. 17:33:39 You just have to create one template, you can stop mining right after that. 17:33:47 It might not be super helpful though. 17:51:28 2019-12-17 17:51:05.896 [RPC1] INFO txpool src/cryptonote_core/tx_pool.cpp:327 Transaction added to pool: txid weight: 2598 fee/byte: 13837.6 17:51:28 2019-12-17 17:51:05.896 [RPC1] INFO txpool src/cryptonote_core/tx_pool.cpp:395 Pruning tx from txpool: weight: 2598, fee/byte: 13837.6 17:51:29 2019-12-17 17:51:05.896 [RPC1] INFO txpool src/cryptonote_core/tx_pool.cpp:399 Pruned tx from txpool: weight: 2598, fee/byte: 13837.6 17:51:29 2019-12-17 17:51:05.902 [RPC1] INFO txpool src/cryptonote_core/tx_pool.cpp:413 Pool weight after pruning is larger than limit: 18446744073709322844/648000000 17:51:56 Manual txn shove onto xmrchain w/ the raw hex, ^ is from the xmrchain daemon. 17:52:32 Looks like we're getting auto-pruned some how. 17:55:12 No, it's an unrelated thing. 17:55:36 Is your txpool full ? 17:55:40 "print_pool_stats" 17:57:11 moneromooo: https://paste.debian.net/hidden/f9a89ae4/ 17:58:53 The 18446744073709322844 says there's a bug in accounting in pool size. 17:59:03 This ought not prevent that tx from being mined though. 17:59:44 If that is the problem, a restart should fix it. Plus relay_tx if you want to not wait 4 hours. 17:59:55 Wait a bit first. 18:00:06 I'm going to look whether there's anything I'd like to get from gdb... 18:00:06 that was from snipas node, not the affected one 18:00:20 OK 18:01:13 but seems his node also doesn't like the tx 18:02:29 Any interesting exceptions ? That is, not the weak pointer one, nor the randomx one ? 18:06:55 I'm out atm so can't look. snipa will be back in ~15m 18:31:15 Sorry, just got back. That error I pasted is from xmrchain, I'll get it's pool size, but it's updating fine overall. 18:31:32 Also, relay_tx isn't playing nice on the affected node, and it's been restarted. 18:45:22 moneromooo - The logs you wanted from the debug: https://pastebin.com/raw/tdqqkdyW Nothing useful in there that I can see offhand. 18:47:57 Yes, looks like al txes (presumably included the one that was said to be lingering) got into the block template... 18:48:33 There's 29 lingering, but yes, they all got injected in that template. 18:49:51 Start another daemon, make sure it's connected to the first one. Wait till the first one relays. See if the new daemon receives that tx. 18:50:34 The queue with the issue just cleared itself, I'm getting our backlogged txnid's to see if they just magically managed to broadcast and got happy. 18:52:10 Interesting, looks like they all just made it onto the network, 2-3 hours late, but they made it there. 19:06:19 so weird 19:50:49 Hello again, I am still struggling with my key-image problem, 19:51:03 I created a new question here https://monero.stackexchange.com/questions/11837/function-ge-fromfe-frombytes-vartime-step-by-step-explanation 19:51:36 I tried to read the whitepaper but it is quite heavy 19:54:28 That reminds me, shen wrote a review of that function. 19:54:50 * moneromooo goes look 19:56:05 I think it is here https://github.com/monero-project/research-lab/blob/master/whitepaper/ge_fromfe_writeup/ge_fromfe.pdf 19:56:42 Oh, good. 20:00:04 Oh, god! :)