Bible Pay

Read 5692 times

  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #120 on: July 02, 2018, 07:32:21 am »
So here is a recap on where we are:

I'm nervous about the background prayers, so I put it back in the foreground serially (during load).  I tested this last night.  1.1.3.7 is checked in for linux and now compiling for windows.

As far as test cases, I did test the paid-proposals filter in prod and it passed.  The two proposals left in Prod are the ones we voted down to enter the replacement proposals.  They fall off after 31 days (since the entry date).

As far as test case coverage, to my knowledge everything else passed.

If anyone has any concerns please apprise us.



EDIT:  Windows version is out also.


Today,  I will consolidate all of our release notes together for the mandatory version and we can assess if we are ready for release.


Please take 1.1.3.7 for a spin to ensure nothing is awry.

« Last Edit: July 02, 2018, 10:34:35 am by Rob A. »


  • togoshigekata
  • Sr. Member

    • 371


    • 23
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #121 on: July 02, 2018, 09:12:27 pm »
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589


  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #122 on: July 03, 2018, 02:42:26 am »
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589

My hash matches.. let me do some sanc testing to make sure we are emitting PODC superblocks.



  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #123 on: July 03, 2018, 04:21:08 am »
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28



  • togoshigekata
  • Sr. Member

    • 371


    • 23
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #124 on: July 03, 2018, 07:25:23 am »
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options


  • thesnat21
  • Administrator

    • 53


    • 5
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #125 on: July 03, 2018, 08:58:05 am »
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28

Oddly I'm not seeing this on all my wallets, only a few i'm trying to figure out why.


  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #126 on: July 03, 2018, 11:25:02 am »
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options

Only in testnet, or in prod?

EDIT: Ill run two nodes in prod on 1138 and see if something should be done if so we can rerelease a patch.

EDIT:  Is there anything in your saved file we should remove?
« Last Edit: July 03, 2018, 11:53:21 am by Rob A. »


  • togoshigekata
  • Sr. Member

    • 371


    • 23
    • September 01, 2017, 10:21:10 am
    • USA
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #127 on: July 03, 2018, 11:53:32 am »
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did


  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #128 on: July 03, 2018, 12:23:05 pm »
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did

Try removing or renaming debugmaster=true.  The parser probably interpreted that wrong.

Im using 231K on linux and 269K on windows in Prod on 1138 after running for a half hour and being fully synced.

21 Meg means something is really wrong on the node.  Could be those settings...

My log is clean now but I did release a small patch, but it only removed 2 messages.



  • thesnat21
  • Administrator

    • 53


    • 5
    • March 28, 2018, 06:37:05 pm
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #129 on: July 04, 2018, 09:18:22 am »
submitted fix for the recent transaction issue to github.


  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #130 on: July 05, 2018, 09:06:52 am »
submitted fix for the recent transaction issue to github.

Thanks, will look into this asap!

Been making great progress on stratis, need to put this down...




  • Dynaxius
  • Newbie

    • 2


    • 0
    • July 28, 2018, 04:52:41 pm
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #131 on: August 14, 2018, 02:57:03 pm »
Hi, Rob. Is the current plan for the upcoming BBP migration involving Stratis to create a fork of Stratis, or are you hoping to leverage the new sidechain tech they have released in recent months and actually deploy BBP beneath the Stratis Blockchain?

https://academy.stratisplatform.com/Sidechains/sidechains-introduction.html


  • Rob Andrews
  • Administrator

    • 1281


    • 22
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« Reply #132 on: September 07, 2018, 07:42:20 pm »
Hi, Rob. Is the current plan for the upcoming BBP migration involving Stratis to create a fork of Stratis, or are you hoping to leverage the new sidechain tech they have released in recent months and actually deploy BBP beneath the Stratis Blockchain?

https://academy.stratisplatform.com/Sidechains/sidechains-introduction.html

We ported our POBH and kjv.cpp into stratis, so not sidechain, but actual real chain, and full compatibility with biblepay-qt production.  Except we haven't started porting the governance module yet, so you cant have a stratis Sanctuary (yet).