07:27:24 <Mysterion> wait moneromoooo are you the author of primo?
07:28:12 <Mysterion> just noticed you commenting on github on the monero PR
10:04:13 <sech1> The test is going smooth so far. I've prepared pull-requests for master and release-v0.17 branches to support p2pool.
13:55:33 <sech1> I think it doesn't make much sense to continue with testnet, I'll start mainnet testing tomorrow. We've already confirmed that p2pool can mine blocks and payouts are spendable, mainnet testing will be focused on how stratum server performs
14:42:02 <hyc> sounds good
14:42:47 <hyc> and agreed, I don't see what else we can get out of testnet testing
14:43:02 <hyc> we need to see how things work under real load
14:52:40 <hyc> is there any way 3rd parties can observe a p2pool operation and see how many wallets it's paying out to, or when it will be maxed out in terms of txn size?
14:53:05 <hyc> just to avoid trying to use a maxed out pool
14:53:39 <selsta> sech1: I think the zmq changes won't be included in the next release
14:53:47 <selsta> too large to get reviewed quickly
14:54:14 <hyc> yeah I had a feeling it was too large as well
14:54:35 <hyc> but would be nice to get soon. perhaps the following point release, if there is one?
14:55:45 <selsta> sure
14:57:10 <hyc> at the same time, I can see omitting it as just prompting a lot of people to roll their own until an official release is available
14:57:26 <hyc> I mean, I'd switch my solo miners to p2pool immediately
14:59:08 <sech1> I didn't expect it to be included in the next release. Wallet fixes would be nice though
14:59:28 <hyc> yeah the wallet patches were trivial
15:05:31 <selsta> yes the wallet patch can be included
15:45:24 <moneromoooo> Just to see what'd happen, I ran monerod, then p2pool, then xmrig, right after one another. moenrod had been down for 2.5 hours, so it took a bit to sync.
15:45:43 <moneromoooo> Nothing's happening. xmrig not mining, p2pool not logging anything after startup.
15:46:14 <moneromoooo> (but monerod synced and is ready)
15:47:03 <moneromoooo> Ah, p2pool just logged a new block. Still no mining happening.
15:47:22 <moneromoooo> Restarting xmrig: connection refused
15:48:09 <moneromoooo> netstat shows p2pool is listening on 37891
15:49:23 <moneromoooo> No 3333, but p2pool is set up to listen to this with stratum via command line.
15:49:39 <sech1> did you get latest?
15:50:03 <sech1> I changed ZMQ RPC name, you need to recompile monerod using p2pool-api branch
15:50:12 <moneromoooo> The only "weird" thing I see is: P2Pool get_miner_data RPC response is invalid, skipping it
15:50:32 <moneromoooo> Same binaries that were working fine before I stopped eveything 2.5 hours ago.
15:51:20 <moneromoooo> get_miner_data was probably erroring out due to busy while syncing
15:51:40 <sech1> if get_miner_data fails then p2pool fails to start
15:51:56 <moneromoooo> Well, it started, and logging when monerod finds a new block.
15:52:36 <moneromoooo> I restarted p2pool now, and it seems to be fine.
15:52:58 <moneromoooo> ie, xmrig can connect to it and mine, and got one share accepted.
15:53:13 <sech1> yeah, it doesn't handle errors at startup well. It should've stopped on that error and exited instead of trying to do something
15:53:24 <moneromoooo> This is fa3146a8f3ad13a6211a98ee4f35bbe18b618ce3 on p2pool.
15:56:43 <sech1> p2pool could probably keep trying to call that RPC until it succeeds