[00:00:18] setting different ports and datadirs [00:07:44] ill have a look at that and the dao review from @salmonskinroll tomorrow in the morning [00:15:20] from what ive quickly checked now the max reorg check is timestamp based, maybe if you generate the blocks too quick they share the same timestamp [00:15:28] @prole [08:40:30] *** Joins: navcoin-bot4 (~navcoin-b@nav.community) [08:40:33] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Read error: Connection reset by peer) [08:41:24] *** navcoin-bot4 is now known as navcoin-bot [09:13:59] Ah okay [09:14:15] I'll have a look from that angle [11:49:41] @aguycalled is there a way to cancel a proposal/request? [11:50:03] no, the network should reject it [11:50:07] Like a way to sign a tx that tells the network to stop counting votes for a proposal/request [11:50:25] I mean, canceled by the creator/owner. [11:50:39] it's not supported [11:51:06] I see, how difficult would it be to add that to the dao logic? [11:51:23] I'm assuming it would also require consensus change [11:51:48] yes, but it would not be dffficult and can be put together with the whole dao extension [11:51:58] But of course canceling a proposal would not refund the 50 nav fee. [15:05:31] @salmonskinroll on your network with inconsistent cycles, did any of the nodes see a reorg? [15:08:39] wasn't monitoring it, how can i tell? [15:09:27] do u have the logs? i can have a look there [15:10:56] yes, i'll pm you all 6 logs lol [15:11:14] just the debug or error log as well [15:15:50] debug is enough [15:20:45] files quite big as i didn't clean it up before doing DAO tests 😛 [15:21:11] are u able to replicate the issue? [15:21:42] well, it's more like it's always there now and i haven't noticed a pattern [15:21:47] will keep trying [15:22:02] im also doing my tests [15:53:05] so even if a reorg happened, it's not suppose to do that right? [16:06:48] yep [16:06:52] state should be consistent [17:31:36] https://cdn.discordapp.com/attachments/416000318149754881/629702166478585856/unknown.png [17:31:54] in devnet this happened automatically without me doing anything, it was 30 before [17:32:19] what does listconsultations show? [17:33:53] only my 2 consultations [17:33:59] that i submittted [17:34:17] interestingly this happened i think only when im stakign with 1 node only [17:34:42] and now i can't propose a change back [17:34:43] https://cdn.discordapp.com/attachments/416000318149754881/629702952935882776/unknown.png [17:35:15] workign on replicating it [17:35:28] what does the log say when the proposal fails? [17:35:43] also could you do getconsensusparameters ? [17:36:10] [ 2, 150, 2, 4, 4, 1, 10000000000, 150, 5000000000, 5000, 7000, 7000, 5000000000, 6, 5000, 7000, 7000, 0, 8, 500, 2000, 250000000, 10000000000, 10000000 ] [17:38:08] 2019-10-04 15:37:41 ERROR: IsValidConsultation: Invalid consultation 3705e7993a2e4c85b2a256186d58efcd6b555308256f3da801b1481fa7f32f2d. There already exists an active consultation about that consensus parameter. [17:38:19] i might have created one when i saw it was 2 [17:38:36] but it's not being voted on [17:38:37] https://cdn.discordapp.com/attachments/416000318149754881/629703934675648512/unknown.png [17:43:58] will try to replicate it and log it on github [19:22:21] @salmonskinroll could you try with my last commits [19:23:03] sure, give me some time, so many things to test now lol. [19:23:11] sure no rush [19:23:17] questions [19:24:20] "found support, waiting for end of voting period" should be when support is found during a block cycle right? or it's when support is found and block cycle ends then the very next cycle will display waiting for end of voting period [19:25:01] another question, for voting number say between 0-99, are relies limited to int? [19:25:23] yes limited to int [19:26:38] when it says "waiting for end of voting period" it means it has already the necessary amount of votes to pass to the next state, but it will only change once the cycle finishes [19:27:17] okay, not sure if i saw something wrong, just checking [19:49:41] logged it on github, do you need the debug file? @aguycalled [19:54:39] did you do it with the last commits? [19:54:54] you should see the previous error entry with an extra hash [19:56:39] no that was the old DAO before any of your new commits. did the new commit fix it? what do you mean by extra hash? [19:58:17] it adds extra log [19:58:41] it should show something like 2019-10-04 15:37:41 ERROR: IsValidConsultation: Invalid consultation 3705e7993a2e4c85b2a256186d58efcd6b555308256f3da801b1481fa7f32f2d. There already exists an active consultation xxxxxxxxxxxxx about that consensus parameter. [19:59:28] okie dokie, building the new commit now and will retry it [19:59:52] but still weird that it just happened on itself [20:00:04] yep ill try to replicate it now [20:02:42] something tells me it has something to do with either only having one node staking all the blocks or the title "2nd test 10/4" since i starting doing these two today and this happened [21:14:25] ok, ran with new commit and now the blokc cycle set itself to 1 again, you want the debug log? [21:45:17] i've been able to replicate i [21:45:18] t [21:48:45] okie dokie, i'll leave taht one to you then [21:50:15] i've tried creating consultation, finish consultation, block cycle -> 1 , propose blockcycle -> 15, gets approved, (not block cycle = 15) create a consultation, finish consultation -> block cycle ->, propose blockcyle -> 15 , error, cannot create proposal [21:52:50] not sure if it's all related [22:08:01] should be fixed with my last commit [22:08:11] you might need to start a new chain [22:09:25] is not able to propose new consensus parameter part of the fix as well? [22:09:56] i don't see the initial issue anymore, tried to propose a consensus change and been able [22:10:27] okay, well i'll test it [22:10:42] do you still have the same navcoin address? [22:10:50] what cause it to be set to 1 for no reason? [22:10:58] yup [22:11:18] a missing check, confused the proposal you created with a consensus change [22:11:28] i see [22:24:00] 5993262f1201206a1649a58f4a019849760ee62577840997683f433eb8846ec4 [22:25:46] thanks!