BitShares TESTNET release test-2.0.181018 新测试版本发布
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
Description | Issue | Pull Request |
---|---|---|
Change call_order_update_operation to return order_id | 1269 | 1352 |
Node Functionality
Description | Issue | Pull Request |
---|---|---|
Segmentation fault when running several witness nodes on the same machine | 377 | 1286 |
Performance opt pt 1 | 1079 | 1359 |
Log console output during replay to file | 985 | 1355, FC-76 |
Change replay percentage to total block size processed | 1289 | 1335 |
Improve block generation performance | - | 1251 |
Review and backport EOS patch about unsigned_int unpacking | 993 | 1267 |
Check and port Steem PR 2692: missing FC typenames | 1217 | 1248 |
witness_node uses two incompatible parsers for config.ini | 149 | 1024,1325 |
db_block.cpp: removed unreachable code | - | 1312 |
Cleanup budget_record_object? | 1139 | 1213 |
Change object_id to more than 32 bit | 1088 | 1267 |
More 32 bit to 64 bit changes | 1206 | 1347, 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 fixed | 752 | 1049 |
When signing a block that updates the signing witness's signing key, use correct signing key | 125 | 1203 |
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 time | 1157 | 1266 |
remove verify_account_history_plugin_index() | - | 915 |
inconsistent error message for update_asset_issuer | 944 | 1255 |
Possible to generate a block that is too large | 1136 | 1252 |
remove duplicated line in network code node.cpp | - | 1231 |
Node Plugins
Description | Issue | Pull Request |
---|---|---|
Terminate block production loop when shutting down witness plugin | 1314 | 1332, 1364 |
add dascoin adaptor | - | 1356 |
[ES plugin] Wrong value of additional_data.fill_data.fill_order | 1295 | 1351 |
refine es_objects plugin | 1271 |
Command Line Interface (CLI)
Description | Issue | Pull Request |
---|---|---|
CLI wallet: avoid directly overwriting wallet file on exit | 1109 | 1195 |
cli_wallet crashes when doing import_key on Mac | 1244 | 1248 |
get to_id from to_account instead of get_account_id() | - | 1242 |
Build Process
Description | Issue | Pull Request |
---|---|---|
Integrating cURL into cmake | - | 1329, 1336 |
cli_test doesn't compile on Windows due to using 'sys/socket.h' | 1292 | 1305 |
clean old style codes | - | 1250 |
Unit Tests
Description | Issue | Pull Request |
---|---|---|
Not able to perform testing [100,000 transactions per second] | 1298 | 1337 |
Refactor cli_test | 1192 | 1243 |
Test case failed on chain_test | 1326 | 1346 |
Documentation
Description | Issue | Pull Request |
---|---|---|
API documentation | 780 | 1174 |
Launch BitShares Developer Portal | 1031 | How-19, Dev-41 |
add new doc portals to readme | 953 | 1358 |
add readme to plugins | - | 1319 |
LaTeX project for documentation like C++ ISO/IEC | 1288 | - |
Probably wrong comment | 1301 | 1349 |
Create plugin script | - | 1302 |
add new doc portals to readme | 1363 |
Release Contributors
@abitmore
@botanegg
@cogulvalera
@cwyyprog
Damir from Dascoin
@HarukaMa
@jmjatlanta
@ihla
@liondani
@OpenLedgerDev
@oxarbitrage
@pmconrad
@RichardWeiYang
@ryanRfox
@tsugimoto
@zhuliting
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