Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Value change on "required-participation" throws an error on test-3.1.1 #1786

Closed
liondani opened this issue Jun 7, 2019 · 4 comments
Closed
Assignees
Labels
2f Testing Status indicating the solution is being evaluated against the test case(s) 3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.)

Comments

@liondani
Copy link
Contributor

liondani commented Jun 7, 2019

Describing Current abnormal Behaviour
When I changed "required-participation" on config.ini from value 0 (zero) to 33 and restarted my test witness node like this:

./witness_node --rpc-endpoint 127.0.0.1:8090

I got this error:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injectorboost::program_options::invalid_bool_value >'
what(): the argument ('33') for option 'required-participation' is invalid. Valid choices are 'on|off', 'yes|no', '1|0' and 'true|false'
Aborted (core dumped)

Screenshot from 2019-06-07 16-38-57
^^^ click to see the screenshot!

Expected Behaviour
Normally the node should start without problem and just not producing blocks on a chain where less of 33% of witnesses produce blocks

It makes no sense for "required-participation" to expect a boolean value !!!

PM Same error on main net with "client_version": "3.0.1-2-gf39a2c2a"

Host Environment TEST node

  • Host OS: Ubuntu Linux 16.04.6
  • Host Physical RAM 32GB
  • BitShares Version: test-3.1.1
  • OpenSSL Version: OpenSSL 1.0.2g 1 Mar 2016
  • Boost Version: 1.58

Host Environment MAIN node

  • Host OS: Ubuntu Linux 18.04.2
  • Host Physical RAM 64 GB
  • BitShares Version: 3.0.1-2-gf39a2c2a
  • OpenSSL Version: OpenSSL 1.1.0g 2 Nov 2017
  • Boost Version: 1.65.1
@oxarbitrage
Copy link
Member

Looks like a bug here: https://github.com/bitshares/bitshares-core/blob/master/libraries/plugins/witness/witness.cpp#L67

Should be changed to something more like:

 ("required-participation", bpo::value<uint32_t>()->default_value(0), "Percent of witnesses (0-99) that must be participating in order to produce blocks")

@liondani
Copy link
Contributor Author

liondani commented Jun 7, 2019

yep, seems like that

@oxarbitrage oxarbitrage added the 3d Bug Classification indicating the existing implementation does not match the intention of the design label Jun 7, 2019
@oxarbitrage
Copy link
Member

@liondani will be great if you can give a try to #1787 and check if it is working as expected. thank you.

@pmconrad pmconrad added this to the 3.2.0 - Feature Release milestone Jun 8, 2019
@pmconrad pmconrad added 2f Testing Status indicating the solution is being evaluated against the test case(s) 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.) labels Jun 8, 2019
@oxarbitrage
Copy link
Member

closed by #1787

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2f Testing Status indicating the solution is being evaluated against the test case(s) 3d Bug Classification indicating the existing implementation does not match the intention of the design 6 Deployment Impact flag identifying the deployment process (e.g. Docker, Travis, etc.)
Projects
None yet
Development

No branches or pull requests

3 participants