[19:50:52] *** Joins: navcoin-bot (~navcoin-b@nav.community) [21:00:38] mmm [21:02:12] id have to check the logic, could be something simple like using > rather than >= [21:02:27] is it happenign for every user? or just intermittently? [21:02:50] i had a quick look and could not find what was wrong [21:03:21] can you replicate it? or is it only randomly for some users? [21:03:31] is it a specific OS? or [21:03:54] haven't tried, been busy on the dao and headerspam [21:04:06] okay, do you want me to take a look? [21:04:15] i can try sync a node from scratch here and see what happens [21:04:50] sure [21:05:25] syncing from scratch should be part of our release smoke test list of things to do [21:09:04] okay, syncing 4.7.1 now on OSX [21:09:10] will report back in 3 day [21:09:15] 😅 [21:10:33] lol, i'll do one as well on windows 7. i've done resync from scratch on linux multiple times every now and then and never had a problem. [21:12:07] @aguycalled who are the users are having the problem? Might be worth just getting some more info about OS so we can directly try to replicate their environment if i can't make it happen on OSX [21:12:33] ill ask [21:13:42] windows [21:14:02] which one? [21:15:32] 10 [21:15:57] okay, will try it on 10 as well, running it on 7 for now. [21:36:06] @aguycalled it's still not right after a reorg happens, node 1 and node 2 voting at the same time, disconnect them to make them fork, stop node 1 and reconnect them so node 1 reorgs to node 2, node 1 showing incorrect vote counts as well as not counting any more votes from node 2 [21:36:11] https://cdn.discordapp.com/attachments/416000318149754881/641737618136236053/unknown.png [21:36:52] i haven't seen it again. do you see it straight? or do you need different rounds? [21:37:19] straight? if i understnadyou correctly. [21:37:29] they are on the same block height, but vote count is differnt [21:37:41] like always everytime they reorg [21:37:44] same hash too? [21:37:48] 1 sec [21:38:21] same block hash [21:38:43] https://cdn.discordapp.com/attachments/416000318149754881/641738256760832010/unknown.png [21:38:44] what does disconnect them to make them fork mean? [21:39:35] well i ban each other's ip through the peer window. so they would start staking on their own and i can see that by watching that the blocks they stakes all vote differently [21:46:09] on the side note though, it used to fork all the time even if i don't ban ip, but now they don't fork at all. just an observation. [21:46:33] there should not be a difference on that [21:47:14] hmm, i guess i was lucky this time around [23:07:34] @aguycalled @aguycalled (hmm there are two aguycalled) there isn't a place to show current cfund stats (available funds locked funds etc) in the dao client now. do you think it should be added? or it'll be in the new GUI @mxaddict is working on? [23:07:55] we can add it [23:08:50] who is this user aguycalled#1604 ? [23:08:57] scammer [23:10:03] might want to kick him out of the server [23:22:27] should this be opened again? https://github.com/navcoin/navcoin-core/pull/609 [23:48:11] banned [23:48:32] i'm now able to see the issue disconnecting the nodes and then reconnecting them [23:48:36] @salmonskinroll [23:54:08] Awesome. :) Let me know when it's ready.