[05:39:41] @mxaddict Are you here? [05:41:45] sda6@sda6-Z68X-UD4-B3:~/gitcola/navcoin-core/depends$ make -j8 Preprocessing libevent... autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force configure.ac:129: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are [05:41:46] legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /usr/bin/autoconf failed with exit status: 1 funcs.mk:251: recipe for target '/home/sda6/gitcola/navcoin-core/depends/work/build/x86_64-pc-linux-gnu/libevent/2.1.8-stable-dcc13e8b072/.stamp_preprocessed' failed make: *** [/home/sda6/gitcola/navcoin-core/depends/work/build/x86_64-pc-linux-gnu/libevent/2.1.8-stable-dcc13e8b072/.stamp_preprocessed] Error 1 [05:41:46] sda6@sda6-Z68X-UD4-B3:~/gitcola/navcoin-core/depends$ [07:39:48] @aguycalled i just woke up, haven't checked yet. [07:41:58] @roast you have build-essential installed? [08:15:37] @aguycalled @prole I could not replicate the issue that I experienced yesterday [08:15:42] I'll try again [08:16:07] Can you guys also run full sync with the patch that @aguycalled sent? [08:16:17] Maybe someone else can replicate it. [08:23:47] yes im doing and checking the code [08:30:43] The new sync I did last night did not fail [08:31:00] I've started a new one a few minutes ago [08:31:14] Do you think it's possibly a network issue? [08:31:30] That was the only thing that was different from yesterday's sync [08:31:49] My laptop got disconnected from WAN for a few minutes [08:38:59] i dont think its network related. anyway it should be resistant to those issues and sync flawlessly. [08:41:06] ACK [08:41:09] Will keep trying [09:33:39] which branch or pr? [09:33:47] im still reindexing #539 [09:36:14] It was with the __poll_chk branch [09:36:57] But i don't think it's related to the __poll_chk patch [09:37:04] It looks cfund related [09:40:12] @aguycalled maybe make a PR with the patch you sent here, so we can merge into master and hopefully when people test the RC, maybe we can get additional debug info [11:10:46] @aguycalled Can you make a PR with the patch that you send here? [11:11:16] I mean this: diff --git a/src/consensus/cfund.cpp b/src/consensus/cfund.cpp index aa8f00c2..9ef69440 100644 --- a/src/consensus/cfund.cpp +++ b/src/consensus/cfund.cpp @@ -397,6 +397,8 @@ CAmount CFund::CProposal::GetAvailable(CCoinsViewCache& coins, bool fIncludeRequ CAmount initial = nAmount; CPaymentRequestMap mapPaymentRequests; + LogPrintf("[CFUND] >> Checking available balance for proposal %s\n", [11:11:17] ToString(coins, chainActive.Tip()->GetBlockTime())); + if(coins.GetAllPaymentRequests(mapPaymentRequests)) { for (CPaymentRequestMap::iterator it_ = mapPaymentRequests.begin(); it_ != mapPaymentRequests.end(); it_++) @@ -419,7 +421,10 @@ CAmount CFund::CProposal::GetAvailable(CCoinsViewCache& coins, bool fIncludeRequ continue; } if((fIncludeRequests && prequest.fState != REJECTED [11:11:17] && prequest.fState != EXPIRED) || (!fIncludeRequests && prequest.fState == ACCEPTED)) + { + LogPrintf("[CFUND] >> Substracting %d from payment request %s\n", prequest.ToString()); initial -= prequest.nAmount; + } } } return initial; [11:11:32] yes i just want to include a bit more of log just in case, figuring out what else could help [11:11:40] Ok [11:11:47] Let me know when you have it, I'll review [11:12:08] will have it before my lunch [11:12:09] I'm still running another full sync [11:12:22] Hopefully it fails this time [11:12:28] Last 2 times worked properly [11:44:43] @aguycalled#1820 [11:44:45] About the DNS seed [11:44:56] You have a readme on how to run a mirror? [11:45:25] Also, how does BTC find peers? And does upstream use a DNS seed as well? [11:47:24] ok I managed to complete a docker build 🎉 [11:47:45] I think I was just having memory issues before [11:48:30] @mxaddict you're right this is infinitely more simple to set up compared to lxc [11:49:52] Yes, this is why we switched to docker, it saves so much time. [11:50:02] I built #549 [11:50:03] Good to hear it worked. [11:57:19] So does it not crash anymore? @mc290 [11:59:27] Nope [12:00:58] @prole I approved #549. It doesn't crash anymore but I haven't tested syncing, etc [12:01:49] nice [12:01:56] Hopefully we can get more people building gitian builds now that the process is so simple [12:01:58] #549 also builds for me. im currently still reindexing [12:02:05] up to block 2.6 million [12:02:13] so should be done when i wake up lol [12:02:18] Haha [12:02:26] but no problems so far [12:09:05] https://github.com/navcoin/navcoin-seeder/blob/master/README [12:09:08] @mxaddict [12:09:23] its a fork from bitcoins seeder they also usenit [12:09:26] use it* [12:11:05] I wonder if we could make a way to do peer discovery completely decentralized [12:11:11] I've a json output of the data from navcoin-seeder which i've had running for a few months. [12:11:13] https://api.navexplorer.com/api/network/nodes [12:11:15] I can't think of a way as of yet. [12:13:34] @mc290 that is the idea, make the barrier to entry low, so we can get more help. [12:14:03] Trying to automate most of the dev/build process to get more people onboard [12:14:12] We need all the help we can get [12:14:31] The more 👀 the better [12:15:25] @aguycalled we use libunbound for the dns stuff right? I don't see upstream using it. You know what they use? [12:29:00] libunbound is used for openalias [12:29:40] because we need to check dnssec to prevent usurpation attacks [12:30:23] for the dns seed i think its just a mini dns client [12:30:50] using some standard functions i think [12:31:37] Ahh [12:31:49] I thought we used unbound for the seed stuff [12:31:59] So it's used for openalias, gotcha [12:37:08] https://cdn.discordapp.com/attachments/416000318149754881/595925991080329237/Screen_Shot_2019-07-03_at_10.36.46_PM.png [12:37:36] 😭 [12:38:17] https://www.navexplorer.com/block/2762327 [12:39:24] @prole can you backup your datadir and maybe share with alex [12:39:31] That looks like similar error to what I dot [12:40:11] Can the explorer find itself forked in this same manner? [12:40:11] Also, once you've backed up the datadir, try fixing with : reconsiderblock e5e9e23e134e4bd4b4a88542b4fd771373a6c6420eb3a48a7145dd5c2e1b5692 [12:40:19] If that fixes it, then it's same issue that I had [12:40:41] @prodpeak not sure, only seems to happen on full syncs [12:41:00] I think it's possible, but unlikely, we need to fix it anyway. [12:41:06] Still trying to find out the cause [12:41:14] okay [12:41:38] im still posting the community roundtable article around [12:41:45] ill try to post it somewhere or at least get it uploading [12:41:47] Yeah, I saw that 😄 [12:41:51] I gave some claps 😄 [12:41:55] its gettin pretty late here and my brain is starting to cook [12:42:00] i need to go to bed soon [12:42:10] And liked/tweeted [12:42:23] Ai'ght, ttyl man [12:42:31] 👍 [12:42:53] If you share the datadir, I can maybe also take a look at it to try and debug more [12:43:21] It's hard to nip the bug as it's seamingly random blocks that it happens on [12:46:39] im taring the block, chainstate folders + debug.log for you guys [12:46:45] Thanks [12:56:09] uploading to s3 now [12:59:33] i did reconsider block on the invalid block and nothing seemed to happen [12:59:39] so i did it on the previous block [12:59:53] which is the output of getbestblockhash [12:59:58] and it started syncing again [13:00:15] but it could just have been that it took a while to find some peers because id dropped connections iwth everyone [13:00:25] so i dont know which reconsider did it [13:00:29] and the debug didnt really help [13:00:41] I actually had to unban my peers [13:00:47] right [13:00:55] So I think the first reconsider proly did it [13:00:56] seems mine was able to recover and find peers after some seconds [13:01:04] I see [13:01:19] maybe i hadn't banned everyone yet [13:01:20] 😛 [13:01:34] the tar is about half way uploaded [13:01:37] so shouldnt be too much longer [13:01:43] i will post hte link before i go to sleep [13:02:52] well [13:02:55] the link should be this; https://s3.amazonaws.com/navcoin-bootstrap/invalidblock2762327.tar [13:02:56] Ok, thanks [13:02:58] when it finishes uploading [13:03:05] ACK [13:04:29] also, is it just me or does the status bar not seem to be hte right length? [13:04:37] https://cdn.discordapp.com/attachments/416000318149754881/595932906208231426/Screen_Shot_2019-07-03_at_11.04.13_PM.png [13:04:52] 25 weeks behind and hte bar is only just over half way? [13:05:01] the first block is multiple years ago [13:05:13] so either its incorrect or not linear or something [13:06:56] okay, download finished [13:06:56] https://navcoin-bootstrap.s3.amazonaws.com/invalidblock2762327.tar [13:07:30] im off to bed, will talk in the morning [13:09:07] It's same logic as with BTC, I think the back is for blocks not the time [13:09:32] So it's longer towards the end, as I think more tx data in newer blocks [13:10:14] TTYL @prole [13:11:21] @prole why was the block marked as invalid [13:11:23] ? [13:11:42] could you check in the debug.log? [13:13:47] He uploaded the blocks,chainstate + debug.log [13:14:02] I'm downloading now to see if I can find something [13:20:01] the bootstrap does not use to include the log [13:20:19] ok its here in this [13:21:33] Yeah, he created a custom tar [13:31:54] there's no info on the log why it is invalid [13:32:08] Hmmm [13:32:15] I'm still downloading [13:32:38] But how did it get marked as invalid then? [13:32:49] if the log does not say it i can't know [13:33:13] That's a bummer [13:34:48] @aguycalled is the node that you are running built with gitian? or natively on the host you are testing on? [13:35:07] all my nodes are compiled natively [13:35:26] Hmm, maybe the issue is only on the gitian built bins [13:35:44] I'm not sure if @prole used a natively built or gitian built [13:35:52] But the node that had the issue for me was gitian built [13:36:01] i don't think this is related to your issue [13:36:29] Ok, just trying to eliminate as many variables as possible [13:36:32] e5e9e23e134e4bd4b4a88542b4fd771373a6c6420eb3a48a7145dd5c2e1b5692 is not cfund related [13:37:33] I see [13:38:03] Might not be related to cfund then, maybe the block that got marked invalid on my node just happened to be a cfund related block [13:38:14] But maybe the issue is not actually anything to do with cfund [13:39:04] IE some other code on the node messed up the block data, and then when cfund validatation runs, it marked it as invalid cause of the messed up data [13:40:18] Is there a way to get the RAW data from a block? [13:40:33] IE the block that is marked invalid? [13:40:44] So maybe we can compare to a valid copy of the block [13:40:57] the hash ensures the integrity of the block [13:41:05] if theres a single bit which is wrong then the hash would be different [13:41:19] Hmmm, all data in block is part of the hash? [13:41:31] yep [13:41:37] If so, then why does doing reconsiderblock fix the issue? [13:41:56] some state related issue, threading, dbs... [13:42:04] Hmmm [13:42:06] that's what my intuition say [13:42:10] Ahh, similar to the nBits one [13:42:46] Where some thread issue is causing it to mark invalid because of a timing/order of functions [13:42:55] yes [13:43:01] ACK [13:43:18] actually ive been fighting for some days with something similar in the dao implementation [13:43:39] where vote caches suddenly disappear in random blocks [13:44:42] You think it's related? [13:46:04] they share a random behaviour [13:49:55] Did we ever have this issue in 4.6.0 ? [13:50:03] Or older versions? [13:50:25] Yeah, the randomnes is what's making it hard to pinpoint [13:50:45] maybe the original cfund db bug was not related to the cfund db and was related to this, so that's why it's still happening [13:51:40] Possible [13:52:03] But merging the db was good too, so that if the wallet crashed it would not cause a problem between the dbs [13:52:35] When the dbs were seperated they would possibly have different best blocks right? [13:52:47] yes [13:52:48] I mean if a crash occured and the block data was not flushed to disk yet [18:08:20] @mxaddict Build essentials was installed. The only difference between now and the previous install is that navcoin-core is in my home folder and not with my system files. [18:13:35] I don't think that's the cause [18:13:41] Try installing libtool and autoconf [18:13:57] sudo apt install libtool autoconf [18:18:25] Thanks, I'll try the make -j8 again. [18:19:48] You will need to re-run the ./configure step [18:20:05] As that is where the last error was [18:20:08] 👌 [18:21:06] 👌 [18:58:04] @mxaddict Can't seem to find ./navcoin-qt, closest thing is navcoin-qt.dSYM in the qt folder. [19:00:49] sda6@sda6-Z68X-UD4-B3:~/gitcola/navcoin-core/src/qt$ ./navcoin-qt bash: ./navcoin-qt: No such file or directory [19:01:08] what's the output of make? [19:02:21] where do I find that? [19:03:59] I can scroll up a few lines on terminal, I have run [19:04:02] cd navcoin-core/depends make -j4 cd .. ./autogen.sh ./configure --prefix=pwd/depends/x86_64-pc-linux-gnu [19:06:52] now u only need to do make -j8 [19:07:03] on the same folder as configure and that's the last build step [19:08:44] Thanks @aguycalled 😃 Seems to be doing something. [19:18:22] Seems to have hung. Could my permissions still be wrong? [19:18:22] https://cdn.discordapp.com/attachments/416000318149754881/596026963890536480/Screenshot_from_2019-07-04_01-14-36.png [19:20:48] give it some mins [19:20:51] progress 0.00%, progress increase per hour 0.06% [19:20:54] might be looking for peers [19:21:00] Needs to find peers @roast [19:23:21] progress 0.05%/.50%/hr [19:24:27] https://cdn.discordapp.com/attachments/416000318149754881/596028497127014418/Screenshot_from_2019-07-04_01-23-57.png [19:26:20] Thanks guys. 3 years and 6 weeks to go 😃 [19:30:19] Where lies the code relating to to "create payment request" font size? [19:30:20] https://cdn.discordapp.com/attachments/416000318149754881/596029971856752655/Screenshot_from_2019-07-04_01-28-36.png [19:31:32] Ok, looks like it's working @roast [19:31:36] Nice going! [19:31:59] It gets faster once it gets connected to more peers [19:32:01] And faster peers [19:32:13] Also, once the headers finish sync, you will see an ETA of blocks [19:32:29] You see the header sync progress in the sync UI? [19:32:58] @aguycalled I'm home now, building on this machine [19:33:19] Hopefully I can replicate the issue (Cause if not, I won't feel at ease not knowing the cause of it) [19:33:48] I've installed qtcreator too, so I can debug with the UI [19:34:01] cool [19:34:26] https://cdn.discordapp.com/attachments/416000318149754881/596031006251679777/Screenshot_from_2019-07-04_01-34-00.png [19:34:29] i have 2 nodes syncing from scratch on vps (goes faster than on my laptop) and doing code reviews and working in the dao at the same time [19:34:44] @roast that ubuntu ui looks yuck [19:34:55] May I interest you in "arc-theme" 😄 [19:35:32] Kinda off topic, but that shit brown ubuntu color gives me the creeps 🤣 [19:35:50] @roast [19:35:51] https://cdn.discordapp.com/attachments/416000318149754881/596031361266089986/Screenshot_from_2019-07-04_01-35-08.png [19:35:55] I hate it too. Much prefer Mint Mate. [19:36:12] That's my ubuntu desktop 😄 [19:36:27] In fact, this unity crap sucks. [19:36:38] They ditched unity [19:36:51] That DE you're running is now gnome3 [19:36:58] With a Unity Gnome Extention [19:37:11] But you can make it look like gnome, or like mine 😄 [19:37:16] Well gnome 3 sucks too 😃 [19:37:48] 👌 you have a point, but atleast it's not unity 🤣 [19:42:01] @roast just in case, here are my theme and icon settings: Applications: Vimix-Dark-Laptop-Beryl Cursor: Breeze_cursors Icons: Paper Shell: EvoPop-Azure [19:42:13] Will atleast get rid of the ubuntu smell 😄 [19:44:34] haha [20:05:09] https://cdn.discordapp.com/attachments/416000318149754881/596038737356390467/Screenshot_from_2019-07-04_02-04-47.png [20:05:32] Ping times seem a bit high [20:06:34] Woah [20:06:44] I'll send you a node to try and connect to [20:06:54] See if you get better sync speed [20:07:51] . [20:07:57] where? [20:08:11] I PMed you 😄 [20:24:12] Where is the code relating to the font size on the "create payment request" within the community fund tab? [20:27:15] src/qt/forms/communityfundpage.ui [20:27:38] that's the layout [20:27:44] but the style is defined somewhere else [20:28:08] src/qt/skinize.cpp [20:28:29] https://cdn.discordapp.com/attachments/416000318149754881/596044607616450580/Screenshot_from_2019-07-04_02-27-02.png [20:28:57] BTW @roast if you want to be able to test with some coins [20:29:09] You can run the wallet with -testnet or -devnet [20:29:18] And can play around with some play coins [20:29:39] If you can't connect to any peers, it's fine too, you just need to generate 1 in nav console [20:29:43] To get some coins [20:30:28] -devnet in console? [20:31:07] When you start the wallet [20:31:14] IE ./src/qt/navcoin-qt -devnet [20:31:43] ok. .might do that now [20:32:13] 👌 [20:35:12] no peers [20:35:31] Yeah, just run generate 1 in nav console [20:35:36] It should not need peers [20:35:48] And will give you coins + start staking locally [20:36:16] If you want to use cfund + static staking rewards, run generate 300 [20:36:41] That will make 300 blocks in your dev env [20:36:52] And will enable the cfund + static staking [20:36:58] https://cdn.discordapp.com/attachments/416000318149754881/596046743657906207/Screenshot_from_2019-07-04_02-36-34.png [20:37:51] rich man you are 😄 [20:38:00] Yeah, all them coins just for him 😄 [20:38:01] Hahaha [20:41:16] I should stake every block 😃 [20:41:43] you need to generate a few blocks more so the coins are mature to stake [20:42:26] @roast since you have all coins on that node, and you have no peers, yes, you will stake every single block 😄 [20:42:34] You have monopoly on your network 😄 [20:42:38] I just generated 300 [20:42:48] It's great for testing 😄 [20:43:02] cool [20:43:24] @aguycalled on side note [20:43:32] My node at home works [20:43:44] IDK what's wrong with my node on laptop @ the office [20:43:48] 🤣 [20:43:53] no idea [20:44:18] I wonder if it's something on my hardware [20:44:33] Like bad ram that only get's accessed when I get those blocks loaded [20:44:41] Or something stupid like that [20:45:33] Which would explain why it worked when I changed that strprintf into multiple string + ops [20:47:49] I'm trying again (Sanity check) [20:50:03] @aguycalled Should I add these files to .gitignore? NavCoinQT.config NavCoinQT.creator NavCoinQT.files NavCoinQT.includes [20:50:09] They were added by qtcreator [20:50:10] yes [20:53:30] Ok, so it worked again [20:53:35] I've tested it a total of 3 times [20:53:44] So I think it's something on my laptop that caused the issue [20:53:59] Jesus, I just wasted ~4 hours on that 🤣 [20:54:40] What about issue that @prole ran into, were you able to replicate that one? [20:54:42] I have not. [20:55:23] @aguycalled QtCreator feels nice, but I feel naked without my vim muscle memory 😢 [20:55:46] no i havent got anything wrong [20:56:20] one of my nodes just synced completely from scratch [20:56:45] Yeah, I'm waiting for my 3rd node to sync from scratch now as well [20:56:56] Once this is done, gonna do a full sync with index [20:57:11] did you get the issue with the payment request on the same computer where u got that issue? [20:57:42] Yes, that computer with the stuck payment request was on that machine too [20:57:54] what are the specs? [20:58:17] 4 core 8 thread, 16 GB ram, 512 GB NVMe [20:58:23] So I don't think it's a spec issue [20:58:36] And 8GB swap file on NVMe [20:58:56] It might be the machine has actual hardware problem with RAM [20:59:03] It is kinda old now [20:59:33] It's 4 years old I think and I've had heat/cooling issues on it in the past (Could have speed up the damage to memory) [20:59:52] root@nav-test:~/navcoin-core# rm -rf ../.navcoin4/ root@nav-test:~/navcoin-core# ./src/navcoind -printtoconsole -txindex -addresindex -timestampindex -spentindex [20:59:55] doing now this [21:00:03] ACK [21:01:06] should I create a PR to change -printtoconsole to just -print ? 🤣 that flag is a mouthful [21:01:33] i dont mind having print additionally [21:01:42] but im already used to printtoconsole, just dont disable that one [21:01:48] hehe [21:01:59] Ok, I'll just add as an alias then 😄 [21:03:36] I've created 4 address and given them a label but they don't appear in coin selection. I'm trying to send myself some coins. [21:03:47] Ahh [21:03:53] You have to manuall paste the address [21:04:11] Cause if you own the address, they won't show up in the send (Address book) [21:05:31] Can't seem to get an input address. [21:08:00] OK. The font color is too transparent for my eyes 😃 [21:08:28] managed to transfer 1000 nav to a new address. [21:37:21] @prodpeak can you test this PR when you can? [21:37:28] I think it will be usefull for you [21:37:28] https://github.com/navcoin/navcoin-core/pull/546 [21:39:49] I don't actually use all indexes [21:41:06] Ohh [21:41:19] I assumed you did for the explorer 😄 [21:42:43] I think I only use address index. I used to use spentindex but at some point I swapped. [21:43:25] I think it was quicker for me to go update the previous tx with the spend hash than pulling the old block from the RPC endpoint. [21:44:15] Once I've indexed a block I don't retrieve it from the the navcoin-cli again [21:46:45] 3:34am time to sleep TTYL @mxaddict @aguycalled [21:47:47] @roast why are we on same timezone? [21:47:54] You my neighbor? 😄 [21:48:10] Wher are you? I'm in Perth. [21:48:25] I'm in PH (UTC+08:00) [21:49:20] Ahh, I see you are on the left side of AU 😄 [21:49:30] RIght under PH 😄 [21:49:35] Explains the timezone [21:49:42] The sun is going to come up, Hate that. [21:50:14] cya [21:50:38] Ciao [22:30:11] @aguycalled my node is now synced fully, now testing the indexed sync [22:30:14] 👌 [22:33:26] My node on pr # 549 is fully synced after reconsidering that block I posted [22:34:22] And FYI I wasn't using the gitian build [22:34:38] It was locally compiled on ubuntu 18.04 [22:35:12] was it a completely clean data folder? [22:35:25] No, I was doing a --reindex [22:35:59] From existing data that was up to date [22:36:50] Want me to try a full natural sync with clean data directory? [22:37:23] @prole yes please 😄 [22:37:31] If you have read the thread here [22:37:35] I almost went nuts [22:37:42] Turns out the issue was only on my laptop [22:38:08] I've tested full sync (No index) [22:38:17] Yeah I read it from bed [22:38:18] And am now running a full sync with all indexes turn on [22:38:23] When I woke up [22:38:32] An from the other channel [22:38:34] I hope you got a kick out of it 😄 [22:38:49] Always [22:38:56] 😅 [22:39:29] I'll kick off a full resync now [22:39:32] In the vm [22:39:47] Ai'ght [22:39:53] And also I think on osx locally compiled [22:40:02] If we think it also needs testing [22:40:05] my vps is syncing with all indexes already at height 2222086 [22:40:22] @prole does your gitian built osx still have those artifacting bug? [22:40:36] I haven't checked [22:40:38] I can [22:40:50] it's crazy how quick it syncs compared with my laptop [22:40:51] 👌 [22:40:56] a cheap vps of 2.5eur per month [22:41:07] Well, it can get more than 8 peers [22:41:14] Which will speed it up nicely 😄 [22:41:26] My vps syncs faster than my laptop and pc as well [22:41:35] root@nav-test:~/navcoin-core# ./src/navcoin-cli getinfo { "version": 4060000, "protocolversion": 70020, "walletversion": 130000, "balance": 0.00000000, "coldstaking_balance": 0.00000000, "newmint": 0.00000000, "stake": 0.00000000, "blocks": 2273085, "communityfund": { "available": 8940.49000000, "locked": 0.00000000 }, "timeoffset": 0, "ntptimeoffset": 0, "connections": 9, "proxy": "", [22:41:36] "testnet": false, "keypoololdest": 1562180398, "keypoolsize": 100, "paytxfee": 0.00100000, "relayfee": 0.00010000, "errors": "" } root@nav-test:~/navcoin-core# [22:41:43] only 9 connections [22:41:47] Hmmm [22:42:02] I guess the gigabit internet + enterprize SSD 😄 [22:51:32] Should i still be on PR #549 or is there another patch to test? [22:51:39] (just checking) [22:52:26] I don't think there is anything else that we "need" for release [22:53:06] I guess once we are done with this round of testing, we can do the RC builds on v4.7.0 and release for more people to test with [22:53:51] Also, the __poll_chk PR has been merged into master, so I guess merge master into v4.7.0-rc branch [22:54:10] BTW, have you seen how they do RC releases on bitcoin-core? [22:54:27] I think we could do the same, so RC binaries are on github [22:55:36] @prole [23:16:30] @prole @aguycalled The sun has come up, I'm getting to bed 💤 [23:16:33] TTYL guys [23:20:28] okay [23:20:52] syncing locally built #549 from scratch with new data folder on ubuntu 18.04 [23:20:56] will report back in 3 days [23:20:58] lol [23:35:42] my vps synced with indexes in 2-3 hours from scratch [23:41:12] nice [23:41:19] okay so wait, 549 has been merged right? [23:41:31] should i merge master into the RC branch and test that instead? [23:41:40] and re run gitian build etc [23:42:48] Yeah, I think that is next course of action [23:43:00] Jesus, I said I was gonna sleep, My plan is failing 🤣 [23:46:05] okay [23:46:14] i have merged master into the RC branch [23:46:23] ill compile it on gitian and locally [23:46:35] ACK, I'll start a gitian build as well [23:48:37] I can't wait for Ryzen 3000 series, gonna be great for compiling 😄 [23:48:51] 16 core 32 thread machine with 64GB DDR 😄 [23:49:05] Gonna be a beast at compiling navcoin-core 🤣 [23:49:25] Can't wait to run make -j32 LOL [23:49:48] poor me and my make -j4 [23:49:53] Hahaha [23:50:23] You don't plan on getting one of those ryzen chips? really affordable and high core count [23:50:41] Even the 250$ chips are 8 core 16 thread [23:50:47] i get headaches thinking on having to setup everything again [23:51:03] Hahaha, It would be worth the time though [23:51:25] Or you can go the eazy route, just clone the drive (Or just use the same drive) 😄 [23:51:32] also i don't plan to move out of mac, i have a second laptop with linux which i barely use. only for the strictly necessary things [23:51:42] im a happy apple user [23:51:43] I see [23:51:46] 😄 [23:52:02] If AMD keeps up the good work [23:52:09] They might get some lovin from Apple too [23:52:21] Maybe AMD macbook pro in the future 🤣 [23:52:58] i can't with the trackpad and keyboard feeling of other laptops [23:53:16] What year mac are you using? [23:53:27] I heard the new one is not so good (Keyboard I mean) [23:53:42] https://cdn.discordapp.com/attachments/416000318149754881/596096254367367221/unknown.png [23:53:53] I'm a mech keyboard kinda guy myself [23:54:06] Cherry MX Blue is my favorite keyswitch [23:54:13] 5 years already [23:54:18] and still going quite good [23:54:23] Yeah, so you have the good keyboard [23:55:38] I can't use the new mac's either, cause no ESC key (They replaced top row with a touch screen) [23:55:47] Which I think is a step in the wrong direction [23:55:53] i also have a purism [23:56:25] this is my second laptop which i barely use [23:56:56] https://cdn.discordapp.com/attachments/416000318149754881/596097069005930496/unknown.png [23:58:20] bought the librem 5 too, still waiting for the release [23:58:56] i checked the site [23:59:01] Looks like a nice work machine [23:59:07] Why don't you use it much? [23:59:53] hate the feeling of the keyboard and trackpad