BitShares TESTNET release test-2.0.181018 新测试版本发布

in bitshares •  11 months ago 

Release Notes

The BitShares Core software on the TESTNET has been updated to the TEST-201810 Feature Release. The Core software is used by validation nodes which perform consensus of all transactions on the BitShares blockchain. This release includes new features, optimizations, and bug fixes but does not include any changes to the consensus protocol.

No action is required if you do not operate a validation node or the command line interface (CLI) wallet.

Numerous performance improvements have been made to the software that will benefit all operators of validation nodes including block producers, seed nodes, and API nodes, especially those using the Elasticsearch plugin.

Documentation for BitShares developers may be now be found at the new BitShares Developer Portal (https://dev.bitshares.works).

Who Should Upgrade?

No upgrade is required by any operator of a validation node. Yet many operators will benefit by upgrading.

All operators will benefit from performance improvements (915, 1327, 1359) and fixes (1024, 1203, 1286, 1325).

Operators of block producing nodes will benefit from performance improvements (1251), safety measures (1252), and fixes (1266, 1332, 1364).

Operators of API nodes including Elasticsearch APIs will benefit from improvements to data availability (1351, 1352) and performance (1049, 1271, 1356).

Users of the command line interface (CLI) wallet will also benefit from improvements (1195, 1248).

Upgrade Process

Precautions

No special precautions or hardware are expected to upgrade in this release.

How to Upgrade from Source Code

Obtain the Source Code

The source code may be obtained by checking out:

Build the Binaries

The binaries may be built by using your pre-existing process, or by following the standard instructions that can be found in the README.md file.
Platform specific notes

REVIEW: For building under Windows, please checkout 2.0.180823-fix-windows-build tag.

REVIEW: For more information on the macOS binary, see https://github.com/jmjatlanta/bitshares-core/releases/tag/2.0.180823

Deploy the Binaries

Your standard process for deploying the node software may be used. No additional requirements or precautions will be required to deploy the new release.

How to Upgrade with Docker

REVIEW

CLI Binaries for Windows

A binary of the command line interface (CLI) wallet for Windows is pre-built and available for download here TBD (Checksum TBD).

Changes

The changes for BitShares Core for the 201810 Feature Release are summarized below.

Core Functionality

DescriptionIssuePull Request
Change call_order_update_operation to return order_id12691352

Node Functionality

DescriptionIssuePull Request
Segmentation fault when running several witness nodes on the same machine3771286
Performance opt pt 110791359
Log console output during replay to file9851355, FC-76
Change replay percentage to total block size processed12891335
Improve block generation performance-1251
Review and backport EOS patch about unsigned_int unpacking9931267
Check and port Steem PR 2692: missing FC typenames12171248
witness_node uses two incompatible parsers for config.ini1491024,1325
db_block.cpp: removed unreachable code-1312
Cleanup budget_record_object?11391213
Change object_id to more than 32 bit10881267
More 32 bit to 64 bit changes12061347, 1374
Remove definition of unused symbol_type-1235
Update application.cpp-1345
application.cpp: minor optimization-1327
Call order and bitAsset related code refactory-1306
Re-add enable-subscribe-notify-all option after GUI issue fixed7521049
When signing a block that updates the signing witness's signing key, use correct signing key1251203
remove unused variable _consecutive_production_enabled-1294
Check Steem issue 2658: Not producing block because node didn't wake up within 500ms of the slot time11571266
remove verify_account_history_plugin_index()-915
inconsistent error message for update_asset_issuer9441255
Possible to generate a block that is too large11361252
remove duplicated line in network code node.cpp-1231

Node Plugins

DescriptionIssuePull Request
Terminate block production loop when shutting down witness plugin13141332, 1364
add dascoin adaptor-1356
[ES plugin] Wrong value of additional_data.fill_data.fill_order12951351
refine es_objects plugin1271

Command Line Interface (CLI)

DescriptionIssuePull Request
CLI wallet: avoid directly overwriting wallet file on exit11091195
cli_wallet crashes when doing import_key on Mac12441248
get to_id from to_account instead of get_account_id()-1242

Build Process

DescriptionIssuePull Request
Integrating cURL into cmake-1329, 1336
cli_test doesn't compile on Windows due to using 'sys/socket.h'12921305
clean old style codes-1250

Unit Tests

DescriptionIssuePull Request
Not able to perform testing [100,000 transactions per second]12981337
Refactor cli_test11921243
Test case failed on chain_test13261346

Documentation

DescriptionIssuePull Request
API documentation7801174
Launch BitShares Developer Portal1031How-19, Dev-41
add new doc portals to readme9531358
add readme to plugins-1319
LaTeX project for documentation like C++ ISO/IEC1288-
Probably wrong comment13011349
Create plugin script-1302
add new doc portals to readme1363

Release Contributors

@abitmore
@botanegg
@cogulvalera
@cwyyprog
Damir from Dascoin
@HarukaMa
@jmjatlanta
@ihla
@liondani
@OpenLedgerDev
@oxarbitrage
@pmconrad
@RichardWeiYang
@ryanRfox
@tsugimoto
@zhuliting

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Hi @fox, I'm @checky ! While checking the mentions made in this post I noticed that @botanegg, @cogulvalera, @cwyyprog, @ihla, @pmconrad and @zhuliting don't exist on Steem. Did you mean to write @cogutvalera, @iela and @mrconrad ?

If you found this comment useful, consider upvoting it to help keep this bot running. You can see a list of all available commands by replying with !help.

Hi @fox, Great job ! Well done ! Thanks a lot for your efforts and time !

please fix typos in mentions as @checky bot suggested,

me @cogutvalera

Thank you very much !

Indeed great work and great effort to keep the reports coming here!

Can't resist a STEEM tip ... :)
Perhaps they are GitHub usernames for example can do this instead
[@pmconrad](https://github.com/pmconrad)

will give you

@pmconrad (a link to GitHub profile)

typo only for me was there I think, my username is @cogutvalera (not @cogulvalera) and in github the same username I've https://github.com/cogutvalera

I wish my account name were fox... jealous