Skip to content
This repository was archived by the owner on Oct 4, 2019. It is now read-only.

v0.18.1

Choose a tag to compare

@afalaleev afalaleev released this 02 Jul 11:03
2e71565

Software release notice

Golos•Core is planning to release new SoftFork version 0.18.1.
This page provides a brief outline of some fixes and improvements in this version.


Added ability to interrupt a replay-procedure at any time

Bug description:
In case a replay-procedure was interrupted, then the restart of that procedure was performed from very beginning. It was no matter at what time the interrupt occurred. Because of the replay-procedure was taking too long, this was an inconvenience to users.

Solution:
It was decided to keep a system state immediately before interrupting the process. This allows users to rerun the process right from the point it was stopped.

Added flag for preventing automatic replay-procedure call

Problem description:
Sometimes users accidentally run wrong version of golosd that resulted in automatic restart of a replaying procedure and corruption of shared_memory.bin file. Moreover, there was no any way to repair the corrupted file.

Solution:
New flag replay_if_corrupted = false has been implemented in configuration file that prevents automatic replay-procedure call. The flag is set to “true” by default.

Improved way of setting dates in cli_wallet for proposed transactions

Problem description:
When were creating proposed transactions, it was necessary to specify the dates in full format. This was not always convenient.

Solution:
At now it is enough to specify an offset in seconds and then cli_wallet application itself will calculate the date relative to current time.
For example, a command line for specifying offsets will look as follows:

propose_builder_transaction 0 alice test "memo" "+3600" "+1800" true

Fixed bug in get_open_orders method of cli_wallet application

Bug description:
The get_open_orders method call was terminated every time with an error message, no matter when this interruption happened.

Solution:
This bug has been fixed in the get_open_orders method. At now the method returns correct result.

Fixed bug due to which the get_discussions_by_XXX methods returned incorrect results

Bug description:
Each method of the get_discussions_by_XXX family from tags plug-in always returned an empty result when an old post was specified by using start_author and start_permlink parameters.

Solution:
The bug has been fixed in the tags plug-in. At now all of get_discussions_by_XXX methods return correct results.

Renamed environment variables which are passed to the script golosd.sh

Problem description:
Some environment variables had kept their old names with STEEMD prefix, and and as a consequence of that, confused users.

Solution:
The environment variables which are passed to the script golosd.sh and having names starting with STEEMD prefix, were renamed in accordance with this table.

Old variable name New variable name Meaning
STEEMD_SEED_NODES GOLOSD_SEED_NODES Setting seed nodes file
STEEMD_WITNESS_NAME GOLOSD_WITNESS_NAME Setting witness account name
STEEMD_MINER_NAME GOLOSD_MINER_NAME Setting miner account name
STEEMD_PRIVATE_KEY GOLOSD_PRIVATE_KEY Setting witness private key
STEEMD_RPC_ENDPOINT GOLOSD_HTTP_RPC_ENDPOINT Setting RPC endpoint for HTTP
-- GOLOSD_WS_RPC_ENDPOINT Setting RPC endpoint for WebSocket
STEEMD_P2P_ENDPOINT GOLOSD_P2P_ENDPOINT Setting p2p endpoint

Variable STEEMD_RPC_ENDPOINT has been splitted into two differ variables named as GOLOSD_HTTP_RPC_ENDPOINT and GOLOSD_WS_RPC_ENDPOINT.
The variable GOLOSD_HTTP_RPC_ENDPOINT uses for setting RPC endpoint for HTTP communication.
The variable GOLOSD_WS_RPC_ENDPOINT uses for setting RPC endpoint for WebSocket communication.

Created script for managing golosd

Problem description:
There was not possible to influence the daemon restart process in a docker container, that created inconvenience to users.

Solution:
Additional script has been created for managing the daemon restart process. In particular, it allows users to run replay procedure of a chain in a docker container. For example, a command line to run a replay looks as follows:

docker exec golos-default /usr/local/bin/golosdctl replay

Fixed bug due to which the get_content method returned garbage in result

Bug description:
The get_content method returned garbage in some fields of result in case either a post or comment were absent in database. Got result confused users.

Solution:
The bug has been fixed in the social_network plug-in. At now all fields in returned result contain zero values in case requested post or comment are absent in database.

Modified list_keys method of cli_wallet application for returning key type information

Problem description:
The list_keys method always returned a list of public-private key pairs without type and owner key information. Lack of such information created inconvenience to users.

Solution:
The list_keys method of cli_wallet application has been modified. Additional fields which contain information about type key and owner name key, have been added to return result of this method.