[00:13:44] So I've added a test here, if anyone is able to review; https://github.com/navcoin/navcoin-core/blob/09b636b3954b1d7374156339da10f6bb1ad91c61/qa/rpc-tests/cfund-fork-reorg-proposal.py [00:14:06] i am actually not able to get the payment request to complete after the proposal is reorganised [00:14:24] i dont know if i am doing the test wrong or i have found a bug [00:14:45] this is what the output looks like for me; [00:15:15] https://pastebin.com/Xge8gBka [00:17:32] The proposal reorg seems to work, both end up on the right chain and the payment request is submitted without problem. But even after ending 5 cycles with both nodes having the paymentrequest vote set to YES the payment request is still reporting votesYes:0 and will go all the way until expired. [00:19:45] so IDK why its not counting the votes. but i can do some additional logging [00:20:43] no error is thrown from the paymentrequestvote rpc command [00:21:00] im putting in some logging of the paymentrequestvotelist [00:24:39] okay seems like the preq is not visible by getpaymentrequest at the time im trying to cast the vote [00:26:14] okay that seems to have fixed it [00:27:10] not sure why i had to end the current and the next cycle before i could vote [00:27:12] is that normal? [00:29:42] nevermind got it sorted [00:50:42] all committed. and ive re-approved the PR [01:39:16] what was it? [01:39:52] @aguycalled A screenshot before I turn off staking for a while. I started with 25000 tNAV. [01:39:53] https://cdn.discordapp.com/attachments/416000318149754881/645422823489142804/err1.png [01:40:29] before or after? [01:40:40] Before. [01:40:49] does it change after a while? [01:40:59] Staking is now offf [01:41:00] (once turned off) [01:41:39] I'll wait a few cycles then turn it back on and send a screenshot. [01:42:26] just check if it changes before turning it on [01:42:32] otherwise ill have a deeper look [01:42:33] ok [01:46:58] https://cdn.discordapp.com/attachments/416000318149754881/645424608782319617/err2.png [01:47:36] I'll turn it on [01:48:11] Staking is now on [01:48:43] I'll wait for a stake [02:07:41] https://cdn.discordapp.com/attachments/416000318149754881/645429820477669376/err3.png [02:08:31] i'll run repair wallet and see what happens in about 10 minutes [02:13:45] Sunchronising clock [02:16:09] https://cdn.discordapp.com/attachments/416000318149754881/645431950382858240/err4.png [02:16:33] everything looks good. [02:17:00] now I'll start staking again and see if the counters stay correct. [02:55:49] This is after a few stakes and orphans. [02:55:50] https://cdn.discordapp.com/attachments/416000318149754881/645441935573516289/err5.png [02:57:03] AFK for a few hours. Cleaning up mums yard 🙂 [02:57:31] I'll let it run and see what happens by the time I return. [06:20:40] https://cdn.discordapp.com/attachments/416000318149754881/645493484631097364/err6.png [06:21:32] 24tNav variance. [07:51:09] Is anyone here able to help with this investigation into syncing from the genesis block on the mainnet? https://github.com/navcoin/navcoin-core/issues/627 [07:52:01] any hardware / operating system / config settings combinations appreciated [11:25:58] @prole @aguycalled about the setup that binance is running, they use Ubuntu 16.04 right? Do they have specifics on why they are using the older LTS? [11:26:26] IIRC there is an issue with building navcoin-core on 16.04 that @prodpeak ran into. [11:30:26] yes they build with —disable-hardening iirc [11:30:32] bittrex too [11:31:10] i dont know the reasoning [12:05:30] I see, so it works with hardening disabled. [12:47:12] @mxaddict gitian builder is failing on your updated-main-menu branch [12:48:13] https://build.nav.community/binaries/updated-main-menu/log/win/build.log [12:48:31] I'll check it out. [12:50:33] Looks like the qtsvg required tar is missing [12:50:53] https://github.com/navbuilder/autobuilder/blob/master/build.sh [12:50:54] Which means the build sources dir needs to be cleared and it should pass. [12:50:56] this is how i build [12:51:12] Or just need to delete the qt tars frkm sources cache [12:51:21] isnt this handled in gitian? [12:52:01] The gitian builder only checks for the main tar, but since it already has it, it thinks it has all the tars. [12:52:22] if you check the script you will see that i completely wipe the navcoin-core folder [12:52:31] https://github.com/navbuilder/autobuilder/blob/master/build.sh#L10 [12:52:57] Hmmm, I'll check it out when I get to my PC I'm on mobile rihht now. [13:37:35] @aguycalled i check the script and I think you need to wipe out the gitian-builder/inputs/navcoin-core dir as well, but this is only needed if depends has changes. [13:38:37] ok ill add that [18:31:15] i have to nodes syncing from scratch veeery slow [18:47:09] @mxaddict do you think it's possible to fix your gitian build without clearing the inputs folder? [18:48:14] if i clear it i would have to do it for every build and would slow the builds [23:59:37] https://github.com/navcoin/navcoin-core/issues/631 [23:59:44] https://github.com/navcoin/navcoin-core/issues/630 [23:59:53] two issues i've found while syncing from scratch