[01:06:49] @aguycalled I think I got curl to link properly [01:07:05] Will be pushing after I confirm with some builds and tests [01:07:45] Here are the dependencies after may changes: ldd src/navcoind +1  patch-5 linux-vdso.so.1 (0x00007ffe743ce000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f22cf6bb000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f22cf49c000) [01:07:45] libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f22cf113000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f22ced75000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f22ceb5d000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f22ce76c000) /lib64/ld-linux-x86-64.so.2 (0x00007f22d07f2000) [09:50:30] @mxaddict do you think you can code Atomic Swaps and ledger/Trezor support for Nav? [09:50:43] That would be a great community fund project [09:53:26] @Juguelio I'll have to read up on that [09:53:32] But if I can, I will 😄 [09:54:02] For cold staking hardware wallets are quite important [09:54:10] Community has been asking for that [09:54:20] And atomic swaps can open several doors [09:54:36] I see [10:06:05] https://github.com/trezor [10:06:52] https://github.com/LedgerHQ [10:16:58] I don't have those wallets, I might have to buy 1 so I can code for it [10:22:22] it can be part of a community fund request. [10:23:11] if you are willing to start I will donate the cost of a ledger/trezor I am sure other users will contribute [11:25:33] I have a ledger I can donate to someone of they want it [11:52:33] First things first, I need to check if I can do what you want 😄 [11:52:50] Don't wanna commit to it if I won't be able to finish [12:35:21] Yes... obviously...please check and let us know... [12:35:44] It would be awesome to have hardware wallet support [12:38:40] 👍 [18:18:10] @prole @aguycalled should I merge this? Seems simple enough https://github.com/navcoin/navcoin-core/pull/475 [18:18:53] can you? [18:18:55] looks like it misses one approval [18:19:13] but yes, the reason for the test failing is already on master [18:26:08] I think I can, github says I can merge anyway. [18:26:31] I see "you may still merge this pull request." [19:45:10] Mmm let me add the extra review and merge [20:07:20] dunno how i missed that when doing the 4.6.0 rc branch sorry [20:08:24] im also surprised you can see the admin option to force merge without the right number of approvals [20:09:30] the group settings for the 'Development' github team should be read, not write or admin [20:09:31] weird [20:12:47] Yeah, I was wondering why I was given that option [20:14:24] okay lol the base permission for members of the NavCoin organisation was set to Admin [20:14:30] thanks for not deleting all our repo's [20:14:34] 😄 [20:14:34] 😅 [20:14:46] I wouldn't dream of doing that, LOL [20:14:50] ive changed it to read now [20:15:02] Nice, that means I can't mess anything up LOL 😄 [20:15:26] can you just check it for me [20:15:36] if you go to another PR do you see that force merge option still? [20:19:36] No [20:19:40] Not anymore [20:19:51] Also, my reviews don't count anymore 😄 [20:20:56] "Only reviews by reviewers with write access count toward mergeability" [20:21:49] Just wonder.. If he would delete everything, would everything being lost? No Backup? [20:22:30] the ones we would have locally in our computers [20:23:06] Thanks so just a older version [20:23:09] ah shit, okay i make it default write access then [20:23:57] @mxaddict now? [20:27:48] Looks ok now [20:27:56] And no more "Admin" stuff [20:28:17] great [20:28:27] https://cdn.discordapp.com/attachments/416000318149754881/576143467928092693/Screenshot_from_2019-05-10_04-28-19.png [20:28:33] im just re-running travis on that branch and will merge [20:40:29] @aguycalled @prole I'm doing final test builds with gitian linux/arm win32/64 osx for patch-5 [20:40:36] And seems to be going good so far [20:40:50] I got the symbol-checks working [20:41:32] And windows builds now spewing the same hashes for builds 😄 [20:42:02] nice, should i kick off a gitian build on it too? [20:45:53] Nah, might be some changes that I add [20:46:01] I'll let you know when ready [20:46:05] kk [20:46:09] Then we can build and compare hashes [20:49:09] https://github.com/navcoin/navcoin-core/issues/476 [20:49:14] @mxaddict @prole [20:49:26] this is a crash reported by @Goku i am not able to reproduce [20:50:09] i'll keep looking at it as it looks critical but would appreciate more eyes looking at it [20:50:43] any more info on the environment? [20:51:00] windows, linux, osx etc [20:51:04] version [20:52:59] Linux Mint 64bit Cinnamon, Wallet v4.6.0 [20:53:10] 👍 [20:53:11] In a VirtualBox [20:53:21] but you were running an old version when it crashed, right? [20:53:38] Ah yes .. just updated [20:54:15] 4.5.2 but not the version on the website But even with a older version it crashed last time [20:55:11] Let me know which infos you need [20:57:36] @Goku what os? [20:57:49] Linux Mint 64bit Cinnamon [20:58:24] Hmmm [20:58:51] Can you past your `lsb_release -a output? [21:00:10] Oh forgott on the guest os is mate. Moment I will do that [21:02:02] i remember when i was testing PR's yesterday on my ubuntu 18.04 VM i saw the alert saying that there was a new wallet version available and the wallet didnt crash for me there [21:02:47] did you see the alert? did it crash when you interact with the alert? [21:03:05] pretty sure i saw it and closed it and it didnt crash [21:03:14] but i can test on that VM again [21:03:58] i am currently having some issues with the bootstrap server which runs ubuntu also. i logged in yesterday to upgrade the server and the 4.5.2 daemon had died. i tried to restart it and the wallet crashes with the error navcoind: chain.cpp:96: CBlockIndex* CBlockIndex::GetAncestor(int): Assertion `pindexWalk->pprev' failed. [21:04:16] so i updated it to 4.6.0 and wiped the data folder and it started to sync. [21:04:54] and i come back this morning and it has stopped syncing at block 594406 and i get the same error when trying to start the daemon [21:05:22] i think its more likely a problem with my server than the daemon but will keep looking at it [21:05:28] Guest:: '''lsb_release -a No LSB modules are available. Distributor ID: LinuxMint Description: Linux Mint 18.2 Sonya Release: 18.2 Codename: sonya''' [21:07:26] could you log the issue @prole navpis have seen lots of them - i always thought because of running low on memory [21:07:40] also what are the specs of the server? [21:07:40] could be, my VM is pretty small [21:08:25] let me check [21:08:35] might be good to have it logged and get it confirmed anyway [21:14:17] I think I ran into that error on my VPS before [21:14:25] I added a swapfile [21:14:29] And it went away [21:26:24] so it makes sense it is because of low mem [21:26:45] actually if a block suddenly has no previous block, it is the genesis block, or it disappeared from memory [21:27:21] @mxaddict added a second bounty-med label to your pr #461, hope i'm not missing any :p [21:33:16] bootstrap server is: 2 GB Memory / 50 GB Disk / SFO2 - Ubuntu 18.04.1 x64 [21:37:08] 1 vCPU [21:37:30] https://cdn.discordapp.com/attachments/416000318149754881/576160844023332874/Screen_Shot_2019-05-10_at_9.37.20_AM.png [21:37:51] i could try upgrading it to 3GB 1vCPU [21:38:19] or maybe 4GB with 2vCPUs is better [21:38:31] $20 a month isnt the end of the world [21:48:03] I'm running a 2GB 2vCPU vps [21:48:13] But I created a 2GB /swapfile [21:48:17] And the node works fine 😄 [22:13:07] @prole @aguycalled what do you think about this: I think if we adjust testnet/devnet to so that the tests pass faster? Like for example, we can have the static staking reward take only 150 (50 per step) blocks instead of the current 300 (100 per step) And I think the same can be done for cfund tests as well [22:20:35] i can confirm i received the dialog on ubuntu 18.04 and dismissed it without crashing [22:20:49] ill install another VM with the mint distro and test there [22:21:49] @mxaddict now much faster is that likely to make the tests? the difference between creating 300 and 150 blocks must be pretty minimal given there's no real POW to do and the blocks are instamined [22:23:50] @Goku can you confirm whether you are using Cinnamon or MATE? [22:23:57] https://linuxmint.com/release.php?id=29 [22:23:59] Not sure, but we add sleep() to the blocks though [22:24:06] Because they are using slow_gen [22:24:11] ah yeah true [22:24:44] So that's like 0.1*150 seconds we could shave off all function calls to activate_staticr and activate_cfund [22:25:01] Host: Cinnamon Guest: Mate [22:25:37] Wallet works in VirtualBox [22:26:32] You mean is crashes on the host machine but works on the guest? [22:28:08] Cinnamon is installed on the Hardware VirtualBox runs with Mate and there runs the wallet [22:28:21] Ok [22:28:31] But in which os does the wallet crash? [22:28:41] Mate [22:29:02] okay, so Mate 64 bit Sonya release [22:29:10] So works fine with linux mint cinnamon but crashes in linux mint mate. [22:29:11] Yes [22:29:22] No [22:29:49] @mxaddict No i dont run any wallet on cinnamon [22:29:57] Ahh [22:30:23] what are the virtualised hardware settings of your VM? how much RAM and Disk space [22:33:21] https://cdn.discordapp.com/attachments/416000318149754881/576174893675315201/20190510_003237-01.jpeg [22:33:36] 50gb space [22:35:38] ram is 4gb [22:36:19] okay, creating VM now [22:36:58] is anyone else experiencing this issue on any other operating systems? [22:38:54] Maybe we can provoce this issue by me again, with a update notification. [22:39:45] the notification is automatically generated when your wallet sees a majority of new blocks with a different version number to itself [22:40:01] so all you would need to do is run the old version again [22:40:05] and you should see the message pop up [22:40:42] Ok will try [22:41:22] im running hte installation for mint now [22:42:10] @Goku if you don't mind me asking, is there a reason you run the wallet in a VM? [22:45:13] Yes more easy to maintain. - Multi wallets on one hardware - by problems easey to rol back - easy to export it to a new system - I can encrypt the whole VB [22:46:22] yeah, if you use the computer for other purposes, its an easy way to make sure the wallet is ringfenced from any other potential malicious software [22:46:23] I see [22:47:14] i have dedicated hardware for my crypto wallets that i don't install any other software on [22:47:28] but i would not run my wallets on my main laptop with all the crap i install on it lol [22:48:53] just FYI it looks like my staking computer also stopped staking a couple of days ago [22:49:07] i haven't upgraded it to 4.6.0 yet [22:49:18] so i can look at hte logs and see if i can find some reason [22:49:39] I haven't upgraded my odroid yet, did a bootstrap this morning and still not able to fully sync [22:50:25] @prole nice, maybe you can share the debug.log? 😃 [22:56:50] Until now I did not get the notification with the old version [23:00:11] @Goku talk about a forced update, the wallet just crashes, LOL [23:00:27] What language are you running the wallet as ? [23:01:08] German [23:03:50] @prole could it be a translation that causes the issue? [23:07:39] could be? [23:08:00] seems like my staking wallet died because some disk error [23:08:24] so i dont think it was the fault of the daemon [23:08:28] I'm testing the wallet now [23:08:32] With a different language [23:10:46] I have 2 wallets running, both crashed at the same time with the notification. And before with the update to 4.5.2, same happened [23:13:18] When do I get the notification with the old wallet? [23:14:52] it happened almost immediately for me on ubuntu [23:16:06] Hmmm still nothing [23:18:16] Can I do something to get it? Delete some files or so? [23:18:44] I just closed 4.6 and started 4.5.2 again [23:23:56] Late here, good night I let 4.5.2 running [23:24:11] okay, ill keep testing here and let you know what i find [23:32:59] @prole, I tried with a "German" wallet [23:33:04] I got the pop up [23:33:09] but wallet did not crash [23:33:21] I set language to "de" [23:33:36] on mint? [23:33:56] Yes [23:34:02] mmm [23:34:07] So I'm not sure what else I can do to help [23:34:18] Logs did not have anything helpful either [23:34:35] what architecture is mint, same as ubuntu right? x86 [23:34:49] I installed x86_64 version [23:34:54] cool [23:35:26] when i run 4.5.2 on mint it wont open [23:35:38] Mate or Cinnamon? [23:35:49] error while loading shared libraries: libcurl.so.4 [23:35:55] Ahh [23:35:59] Mate [23:36:05] You will have to install libcurl4 [23:36:21] I think that's the package that I installed [23:36:22] ah yep [23:37:46] libcurl3-dev [23:37:48]