STEEM Community QA 27-10-2018
Issue / Feature / Commit to be TESTED:
Report from @ura-soul in #witness-support
--
ura.soul 8:50 PM
three odd things i notice here:
- there is a warning about the /shm/ path for shared mem (as far as i know i have always used that path).
- changing the path to /dev/shm/ doesn't stop the warning
- i see an error relating to a standard config param:
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::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'
- the blockchain version shown is 0.19.6 - even though i completely deleted the steem-docker folder and started fresh
seems like there is a cached version of the build on the system
i don't have any notes here on how to clean that out
bobinson 9:09 PM
required-participation ----> this is a value in the config file. What does it say ?
it has to be either true or false and its currently 33 ?
timcliff 9:13 PM
required participation is how many witnesses need to be in a round for it to be considered valid. at one extreme 0% required participation would mean that one witness could keep producing all the blocks, and your node would consider it a valid chain. at the other extreme, if you had 100% required participation, then if a witness missed a block during the round, then your node would consider it an invalid fork
true/false should not be considered valid values. it should be 0-100
correction: it looks like 99 is the highest it is allowed to go
bobinson 9:24 PM
hmm - not sure. I looked at the boost error message above "Valid choices are 'on|off', 'yes|no', '1|0' and 'true|false'"
ura.soul 11:39 PM
Has anyone else seen these errors in this or recent builds?
I haven't seen anyone reporting these so far..
--
Summary
required-participation
configuration option in the config file must be tested. There is a related issue/commits here: https://github.com/steemit/steem/issues/3025
How to test ?
As per the documentation the acceptable values are 0 to 99 and are integers.
The sample configuration file on the other hand shows the following
# Percent of witnesses (0-99) that must be participating in order to produce blocks
false is a bool while the documentation mentions this as an integer.
Scenario1: Compile STEEM blockchain and start the chain with
required-participation
with the default value.Scenario2: Try True/False and report the result.
Scenario3: use zero (0) and report the result.
Scenario4: use one (1) and report the result.
Scenario3 and Scenario4 are going to be interesting as it will be considered as True/False and also between 0-99
- Scenario5: comment the field and report the result.
Build Environment
Config options:
[root@STEEM-QA /mnt/steem/build]$ cmake --DCMAKE_BUILD_TYPE=Debug ..
[root@STEEM-QA /mnt/steem/build]$ rm -f CMakeCache.txt
[root@STEEM-QA /mnt/steem/build]$make -j66
[root@STEEM-QA /mnt/steem/build]$ make -j66 install
[root@STEEM-QA /mnt/steem/build]$ steemd -d /mnt/steem/build/
This auto generated the config file.
Results:
This section will report the results and if possible expected results
*Scenario1: The chain starts without any issues.
Scenario2: Tried with false and the result is below:
[root@STEEM-QA /mnt/steem/build]$ steemd -d /mnt/steem/build/ Error parsing command line: the argument ('false') for option 'required-participation' is invalid
true, on, off all has the same result.
- Scenario3: use zero (0) and report the result. : chain starts without any issues
- Scenario4: same result.
- Scenario5: commented the field and chain started without issues
This section will post the test results. Expected result is not mentioned as I am confused.
Note: I have since used the following to remove old builds of the Steem software:
sudo rm -rf steem
sudo rm -rf /usr/bin/steemd
sudo rm -rf /usr/local/bin/steemd
sudo rm -rf /usr/bin/cli_wallet
sudo rm -rf /usr/local/bin/cli_wallet
However, this did not resolve the issue after rebuilding and re-running.
I did that too ...
for example, I used v0.20.6 as following
git checkout v0.20.6
I'm not sure where I would run that git command, given that I am using SIAB. The git repo release list for SIAB does not include that version: https://github.com/Someguy123/steem-docker/releases
I have run the following though:
./run.sh build v0.20.6
This should work fine. I directly pulled the code from the git repo as follows.
[root@STEEM-QA /mnt/]$
git clone https://github.com/steemit/steem
[root@STEEM-QA /mnt/steem]$
git checkout v0.20.6
HEAD is now at 5d0a432... Merge pull request #3105 from steemit/sp498
[root@STEEM-QA /mnt/steem]$
git branch
master
stable
In the case of SIAB, I think
./run.sh build v0.20.6
does pretty much the same thingRan ./run.sh build v0.20.6 with SIAB and it shows the following. I don't know what does cache means below. I am a Docker n00b!
Step 9/13 : RUN cd ~ && git clone https://github.com/steemit/steem.git && cd steem && git checkout ${steemd_version} && git submodule update --init --recursive && cd ~/steem && cmake -DCMAKE_BUILD_TYPE=Release . -DLOW_MEMORY_NODE=ON -DCLEAR_VOTES=ON -DSTEEM_STATIC_BUILD=${STEEM_STATIC_BUILD} -DSKIP_BY_TX_ID=ON && make -j$(nproc) && make install && rm -rf ~/steem
---> Using cache
I tried with the exact above options and ran the build again and not able to reproduce again. I think there is some cache or left overs from Docker.
Why don't you delete the docker folders and also do
apt purge docker
and try again ?This post has been rewarded with 100% upvote from @indiaunited-bot community account. We are happy to have you as one of the valuable member of the community.
If you would like to delegate to @IndiaUnited you can do so by clicking on the following links: 5SP, 10SP, 15SP, 20SP 25SP, 50SP, 100SP, 250SP. Be sure to leave at least 50SP undelegated on your account.
Please contribute to the community by upvoting this comment and posts made by @indiaunited.
To listen to the audio version of this article click on the play image.

Brought to you by @tts. If you find it useful please consider upvoting this reply.