[03:46:33] okay [03:46:38] good to know, thanks @Goku [03:50:54] @mxaddict id be keen to hear how you get on with the gitian build [03:51:01] im also struggling with that at the moment [03:51:26] and alex, i understand what you mean now sorry. The LXC vm inside my debian VM has no connection for some reason [03:51:35] im looking into the bridge setup again [03:51:44] perhaps something is wrong there [04:23:34] so yeah i think all these problems come from the rc.local not working and hence the network bridge being down between the LXC image and the debian VM [04:23:57] i manually run the commands located in the rc.local file and now i think the gitian build is working [04:24:43] it's got past the depends at least and now it looks like its compiling navcoin binaries from the output of build.log [04:25:04] but of course these settings will go away once the VM reboots [04:25:40] it's good enough for now to manually run, but i will look into why the rc.local is not loading as a service after i confirm the 4.6.0 hashes [04:46:14] i believe you have to enable rc.local. it's disabled by default iirc. [04:47:11] is this debian 8 or 9? [08:09:11] 9 [08:09:48] my gitian managed to build arm, aarch, windows and osx. but still not x86 it hit that same error with the freetype curl not working [08:09:52] back to the drawing board. [08:11:02] f446a8d53f9cea6542cbc6c17c467d5499a065347d8d1fb2eab2b9613e0b9995 navcoin-4.5.2-osx.dmg 50b53408f9f410792512bb7fd4ea25e4484b8560dee060700168c257bad9b6d1 navcoin-4.5.2-osx64.tar.gz 1eaf880ff5fb82e5cb737281b7021a154686f91fa704b27cbb6ec7c2f24d37a4 navcoin-4.6.0-aarch64-linux-gnu-debug.tar.gz 5837fa19f4b5784871f081d06bcef14ff67b9b0bab1037333b7c514fa0e8e652 navcoin-4.6.0-aarch64-linux-gnu.tar.gz [08:11:03] c20b706fe9649d07570e2c21c8ff5331057c7136290c01df2ce6c0cc2b111f15 navcoin-4.6.0-arm-linux-gnueabihf-debug.tar.gz 0ec939fa648a08583a40972d652af3d630f198a9eb38557b94bffabe5eb5b32f navcoin-4.6.0-arm-linux-gnueabihf.tar.gz d99e812e574142913607a20ced1a6691018c15b53629a8ca62b2a383dd94b5b0 navcoin-4.6.0-osx.dmg b6fed840638e553f342ea439d33baf78b070b0b767651c156a7743ae6aa65c7d navcoin-4.6.0-osx64.tar.gz [08:11:03] 5cdc9eef9e394cf015e9da04da17096db871c375f5a9b8be11a230cee7dfc483 navcoin-4.6.0-win32-debug.zip a83e61e7a97d2247e3258909236a95fc84451c53ff83e756223f04e18798099b navcoin-4.6.0-win32-setup.exe 944f6fa5994a90b7fff90a7392d8f56c8ef5909527d12bfdeb120dc03a1eff8c navcoin-4.6.0-win32.zip e3690476ea7b495b3acc9d7e36eb94763809970cf7816b9cda2c546ce1731a0a navcoin-4.6.0-win64-debug.zip 1722d66ae4af60f16424332ca472278e0db8b7ab771685f849efe65d9f37136c [08:11:04] navcoin-4.6.0-win64-setup.exe e9937c91d7383fa540d350f3008813cd2adaa1795e20f224593cbde4b555627d navcoin-4.6.0-win64.zip e8c56e47e99af1d41eb05ee961258c8ca4c1822b7a5e72c7961cb32650f2c72f navcoin-4.6.0.tar.gz [08:12:43] this is building current master after 4.6.0 merge [09:27:44] @aguycalled my latest push to mxaddict:patch-5 fixed my gitian build, I no longer get the glibc errors when running symbol-check [09:28:13] @prole I was able to build with gitian: 78840b54aaecb720444426e1436b3a6c03a5f8c2414bd48bd704ff49fb56266a navcoin-4.6.0-i686-pc-linux-gnu-debug.tar.gz c848129e9e2b283cb6b7488f8932c278b75899a04bad7286f3740d0ece55fc4b navcoin-4.6.0-i686-pc-linux-gnu.tar.gz 6687b598ee7ff34d6f1dc48065825c205d85b21756d9478f942e72e3a98fcd6e navcoin-4.6.0-x86_64-linux-gnu-debug.tar.gz 2bf61601885d293b1516fc681a1ce78c8a375f89c0286a5822f9654a8d446f8e [09:28:13] navcoin-4.6.0-x86_64-linux-gnu.tar.gz d4c802188f9a90bb21957eee3565b10f545458cedcc519e91c457ec99ac4b0dd src/navcoin-4.6.0.tar.gz 6c0cae18d6b954eb7cb31adeaecdf35e92b696bf3fdfdc7c0ad868e85552238a navcoin-linux-4.0.0-res.yml [09:28:40] This is a build with my mxaddict:patch-5 branch [09:29:44] great im building master now and then will go with your branch [09:30:13] @aguycalled , ACK [09:31:30] BTW, I have a concept for the "Error Log" UI PR, have you seen it? [09:34:40] @prole were you able to fix your gitian build? [09:34:51] I'm using Debian 8.9 [09:35:02] And it worked for me [09:35:08] I used the VirtualBox setup [09:44:11] @aguycalled I've updated https://github.com/NAVCoin/navcoin-core/pull/463 with more instances of the repo address. [09:52:30] ive seen it havent looked at the code/tested yet [09:53:20] The ui will look like this when running: [09:53:20] https://cdn.discordapp.com/attachments/416000318149754881/574534084391469057/Screenshot_from_2019-05-05_17-52-46.png [09:54:25] BTW, since we only have a debug.log and no error.log, I had to parse last 500 debug.log entries and check for errors, then add them to this text area [09:55:20] I was thinking of maybe updating the log print functions to also save errors in a error.log so that I can just parse that and not have to worry about debug.log (As it's usually much larger) [09:58:17] my idea was more about showing the output of error() [09:58:36] filtering through error can leave too much unnecesary things [10:02:19] Hmm, Ok, so that means we have to create a new log file then? [10:02:33] Or did I miss an already existing error log? [10:05:34] Arrent calls to error() just passed to logprint and prepended with ERROR: string? [10:07:35] Currently my matching code is just: // Check if it's an error if (line.contains("error", Qt::CaseInsensitive) && !line.contains("ErrorFile")) logLines += line; // Use the line But if I update it to: // Check if it's an error if (line.contains("ERROR: ")) logLines += line; // Use the line This should work as you intend? [10:11:44] This is what the error log UI looks with a logfile that has actual errors from error() [10:11:44] https://cdn.discordapp.com/attachments/416000318149754881/574538712214536193/Screenshot_from_2019-05-05_18-10-49.png [10:14:01] yup [10:14:12] i think it'd be better filtered like that [10:17:33] Roger that [10:17:44] But I have concerns about the performance of the script [10:17:57] It would be more efficient if we had a second log file [10:18:02] with only errors in it [10:18:07] What do you think? [10:18:11] I can add it to the PR [10:23:29] would you still add those lines to debug.log? [10:23:51] Yes [10:24:06] Similar to how apache has access and error logs [10:24:39] So errors would be logged in both the debug.log and error.log [10:25:01] Basically all logs in debug.log, then only errors in error.log [10:25:59] makes sense [10:26:47] my current code increases the memory usage of navcoin-qt when I artificially insert thousands of errors I'm adding more code to remove the old errors once it's loaded 500 errors in the text area [10:26:54] To limit the mem usage [10:27:26] I could see this being an issue if you run navcoin-qt for a month, the mem usage would start to increase [15:01:27] I'm always writing random ' | grep-v' pipes on command line to get to actual errors in debug.log. I love idea of second error.log [15:29:54] @caffeine 😄 [15:30:04] Yes, I think we were all doing that [16:52:12] @aguycalled I've created the changes that we discussed about error log [16:52:16] And pushed the changes https://github.com/NAVCoin/navcoin-core/pull/466 [16:52:51] @caffeine maybe you can help us test this feature? 😃 since you like error.log idea 😄 [17:08:13] @prole were you able to get your gitian build working? [19:04:02]

@prole users hold their private keys no matter which wallet they use. Our gateway to Bitshares network is as decentralised as it can be at the moment. At the end of the year when federated gateways will be in place that will be a step further. Please send me a dm if you like to discuss further. [19:46:11] I ask me how a DEX can do KYC https://crypto-bridge.org/2019/02/26/urgent-announcement-terms-of-service-identity-verification-requirements/ [19:49:15] @mxaddict no i still can not build i686 & x86 i think due to the freetype dependancy not being able to download [19:49:24] the others work [19:50:31] Hmm, that's strange, I was able to build 32bit and 64bit [19:50:53] @prole I was able to build with gitian: 78840b54aaecb720444426e1436b3a6c03a5f8c2414bd48bd704ff49fb56266a navcoin-4.6.0-i686-pc-linux-gnu-debug.tar.gz c848129e9e2b283cb6b7488f8932c278b75899a04bad7286f3740d0ece55fc4b navcoin-4.6.0-i686-pc-linux-gnu.tar.gz 6687b598ee7ff34d6f1dc48065825c205d85b21756d9478f942e72e3a98fcd6e navcoin-4.6.0-x86_64-linux-gnu-debug.tar.gz 2bf61601885d293b1516fc681a1ce78c8a375f89c0286a5822f9654a8d446f8e [19:50:53] navcoin-4.6.0-x86_64-linux-gnu.tar.gz d4c802188f9a90bb21957eee3565b10f545458cedcc519e91c457ec99ac4b0dd src/navcoin-4.6.0.tar.gz 6c0cae18d6b954eb7cb31adeaecdf35e92b696bf3fdfdc7c0ad868e85552238a navcoin-linux-4.0.0-res.yml [19:51:11] What was the error that you got? [19:57:52] i was using debian 9.6 i think [19:57:55] ill try 8.9 [19:58:47] im just running the linux build again to get the error [19:59:30] effectively this [19:59:34] make: Entering directory `/home/ubuntu/build/navcoin-core/depends' Checksum missing or mismatched for freetype source. Forcing re-download. Fetching freetype-2.7.1.tar.bz2 from http://download.savannah.gnu.org/releases/freetype % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 [19:59:35] --:--:-- 0:00:40 --:--:-- 0 Warning: Transient problem: timeout Will retry in 1 seconds. 3 retries left. 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0 [19:59:40] then it tries a bunch of times and times out [20:00:07] and it tries the backup dependencies location on nav.community [20:00:33] i can curl that URL from the debian terminal [20:00:50] so like alex said before, its like netowrking inside the LXC environment isnt working properly [20:01:21] and i guess the only reason why it worked for me before was because i didnt need to update the dependencies [20:02:24] I think if you're unable to do the curl from inside the LXC VM [20:02:56] its something to do with this configuration [20:02:56] https://github.com/NAVCoin/navcoin-core/blob/master/doc/gitian-building.md#building-with-debian-950 [20:03:44] i have my rc.local setup like it suggests for debian 9.x [20:03:56] You can do this: pushd ./gitian-builder make -C ../navcoin-core/depends download SOURCES_PATH=`pwd`/cache/common popd [20:04:15] This should atleast let you download the files, then can build [20:04:33] So you use that to download the files from the debian cli [20:04:54] And if my assumption is correct, then the LXC environment will use those [20:05:18] good idea [20:05:38] Checksum missing or mismatched for freetype source. Forcing re-download. Fetching freetype-2.7.1.tar.bz2 from http://download.savannah.gnu.org/releases/freetype % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 100 1782k 100 1782k 0 0 114k [20:05:39] 0 0:00:15 0:00:15 --:--:-- 174k /home/debian/navcoin-core/depends/work/download/freetype-2.7.1/freetype-2.7.1.tar.bz2.temp: OK [20:05:41] nice [20:06:46] lets see if it works [20:06:50] running build now [20:07:31] Nice [20:07:41] BTW, I think if you missed this step: echo 'export USE_LXC=1' >> /home/debian/.profile echo 'export GITIAN_HOST_IP=10.0.3.2' >> /home/debian/.profile echo 'export LXC_GUEST_IP=10.0.3.5' >> /home/debian/.profile [20:07:48] You might not get networking on the LXC [20:07:57] I guess double check if those are set [20:08:29] looks like it's building i think [20:08:42] check out the big brain on mxaddict [20:08:46] That last note was more for fixing the problem 😄 [20:08:53] 😂 [20:08:59] Hahaha [20:09:10] Well it better be big, I have a big head, LOL [20:09:19] Unless it's like half n half 😄 [20:09:20] thanks bro, i think it's going to build everything now [20:09:24] heh [20:09:58] Half air half brain 😄 (I feel like it is when I have not had coffee, if you know what I mean) [20:10:25] its 8am here and ive just had my first coffee [20:10:31] still feel like by brain is half air [20:10:32] Nice [20:10:34] need more coffee [20:10:51] I'ts 4:10 AM here, I'm getting ready for a shower, then bed, 💤 [20:10:57] jesus [20:11:01] get some rest bro! [20:11:05] Hahaha [20:11:44] Will do, I work usually in late after noon till early morning cause my desk job is support for USA based online business. [20:11:50] ah yeah [20:11:55] So I get enough rest, I just work US time I guess. [20:11:55] Hahaha [20:12:11] thats cool, just looking out for ya [20:12:44] I pushed a few new PRs, maybe you can have a look see? 😃 [20:13:04] when this linux build passes, ill run the whole lot again on the 4.6.0 tag and we can hopefully get these binaries published if everyone matches [20:13:18] yeah ill see if i can tick any off today 😃 [20:13:28] Thanks [20:14:03] The build hashes I sent here were for my PR, so those won't match master for sure ❗ [20:17:03] Want me to build based on master so we can compare hashes? [20:20:44] yeah, kick one off if you can [20:24:24] ACK 😄 [20:32:11] I'm building based on 4.6.0 tag [20:38:30] 👍 [20:50:26] @prole @aguycalled what do you guys think of supporting more international currencies? [20:50:27] https://github.com/NAVCoin/navcoin-core/issues/468 [20:51:05] in regards to the display currency in the wallet? [20:52:19] Yes [20:52:26] Right now we only have USD and EUR [20:52:33] Right? [21:00:03] yeah i think so [21:07:19] @mxaddict lol of course id help test, but I never use the gui. [21:08:43] @caffeine Hahaha 😄 [21:08:53] This PR is for GUI changes though [21:09:21] i mean i could verify that indeed theres a error.log now 😊 [21:11:25] Yeah, true true [21:11:52] That's assuming that you get errors :D, you might have to wait a while [21:12:10] Took me about 30 minutes to see some errors (Orphaned blocks I think) [21:13:10] @prole Here are my build results for arm: 1eaf880ff5fb82e5cb737281b7021a154686f91fa704b27cbb6ec7c2f24d37a4 navcoin-4.6.0-aarch64-linux-gnu-debug.tar.gz 5837fa19f4b5784871f081d06bcef14ff67b9b0bab1037333b7c514fa0e8e652 navcoin-4.6.0-aarch64-linux-gnu.tar.gz c20b706fe9649d07570e2c21c8ff5331057c7136290c01df2ce6c0cc2b111f15 navcoin-4.6.0-arm-linux-gnueabihf-debug.tar.gz [21:13:11] 0ec939fa648a08583a40972d652af3d630f198a9eb38557b94bffabe5eb5b32f navcoin-4.6.0-arm-linux-gnueabihf.tar.gz e8c56e47e99af1d41eb05ee961258c8ca4c1822b7a5e72c7961cb32650f2c72f src/navcoin-4.6.0.tar.gz 2e4fc154a3c3c0cf241b1b053994a252cf9626d7234caf1046ed7cb45c3bffe7 navcoin-linux-4.0.0-res.yml [21:16:38] I get >10 of these a day, every day: 2019-05-05 19:59:55 ERROR: AcceptBlockHeader: block 0d13ed4db56e3841ed22a2db13a1a366acdc4f804cb7c8efb83865f4a26083cb is marked invalid. FWIW [21:17:42] i dont know enough to know if that is 'bad'. [21:27:43] That looks like an orphaned block was sent to you wallet by a peer 😄 [21:28:09] So it's technically an error, but that a fatal one [21:28:18] So error.log is working for you then, good to hear [21:51:25] @mxaddict those match mine [22:05:49] Nice [22:05:54] Still building the rest [22:45:41] @prole here are my linux hashes: 84609ed6a0fd23d0b8111d38c7b6f37a59e91d51352d481110e919dae5faf16b navcoin-4.6.0-i686-pc-linux-gnu-debug.tar.gz 5cbba74983c5cdc39d29f726a62b1ad8e3de1c619d5e4117a68bd96883062e1d navcoin-4.6.0-i686-pc-linux-gnu.tar.gz 0d27053136a258bcd989b3265eb47164bda4749fbbac8a4147c1e817d0b8bdd7 navcoin-4.6.0-x86_64-linux-gnu-debug.tar.gz a82ca18c2a3767a1f895080632e43fe65c46465eaad8354ad983d44885f210ba [22:45:41] navcoin-4.6.0-x86_64-linux-gnu.tar.gz e8c56e47e99af1d41eb05ee961258c8ca4c1822b7a5e72c7961cb32650f2c72f src/navcoin-4.6.0.tar.gz ceaa2fbd2f343795d5780f5fff63605703ca40fd87847f5bc7965ed97c2d6c2f navcoin-linux-4.0.0-res.yml