v2.0.0 rc2 #104
Merged
v2.0.0 rc2 #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge 1.6.2
When a shutdown signal is handled the sig_set is 1) canceled and 2) destroyed. This means that signals are no longer handled by boost::asio and revert back to default behavior. If someone accidentally hits ctrl-c a second time during a long shutdown they run the risk of leaving the database dirty as that second ctrl-c will be insta-kill. This patch changes the behavior and keeps the sig_set active forever. This means that even after the first handled async_wait() on the sig_set (that starts an appbase quit), additional signals in the set are effectively “blocked” (not posix blocked, but blocked in the sense they are consumed and queued by the sig_set that is not being async_wait()ed on)
…n_17x appbase: Block (queue) exit signals during shutdown - 1.7
there is no tag or branch named "1.6.2", I think it should be "v1.6.2"?
Wrong tag/branch name
The previous fix for blocking signals during shutdown seems to have problems on older platforms/compilers/stdlibs like gcc6. To be completely frank I couldn’t quite pinpoint the exact cause but I highly suspect it is something to do with the application instance being static and thus the ordering of static destructors being unfavorable. I’ve changed the implementation such that during startup a separate thread is run that catches the signals but after startup that thread is retired and signal handling is then handled on the main io_service. Signals end up being blocked (queued) until destruction of application’s io_service because the async_wait() will hold a shared_ptr to the signal_set. The implementation ends up being a bit long winded but means there are no shenanigans trying to clean up threads after main() has fully returned.
appbase: rework blocking (queuing) exit signals during shutdown - 1.7
Update to appbase with FIFO pririty queue - v1.7.x
… is set correctly
… is set correctly
- Fix small memory leak in net_plugin. - Add additional deadline checks to transaction authorization.
appbase: ensure ctrl-c during startup handled correctly - 1.7
- Fix small memory leak in net_plugin. - Add additional deadline checks to transaction authorization.
Signature cpu usage - v1.6.x
Signature cpu usage - v1.7.x
Consolidated Security Fixes for 1.6.3
…mnibus Consolidated Security Fixes for 1.7.0-rc2
Bump version to 1.6.3
Bump version to 1.7.0-rc2
Merge 1.6.3
…avail_ram.py long running test
…ntract Add back integration_test contract; fixes nodeos_under_min_avail_ram_lr_test
Somewhere along the line nodeos picked up a dependency on libicuuc
add libicu as dependency for .deb packages
[1.8.x] CI platform directories
…later via app post
Post State history callback as medium priority - 1.8
ensure GMP is always dynamically linked - 1.8
[1.8.x] Unpinned CI fixes
[1.8.x] 10 second sleep to address heavy usage wait-network bug in Anka
Bump version to 1.8.6
Merge release 1.8.6 to master
Art17
force-pushed
the
develop-v2.0.0-rc2
branch
from
3d5f15b
to
f4f32fd
Compare
…to develop-v2.0.0-rc2
Art17
force-pushed
the
develop-v2.0.0-rc2
branch
from
f4f32fd
to
9061673
Compare
added 3 commits
December 4, 2019 15:40
…to develop-v2.0.0-rc2
Alladin9393
approved these changes
Dec 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(EOSIO#8042) [2.0.x] dockerhub | eosio/producer -> eosio/ci
(EOSIO#8050) Add greylist limit - v2.0.x
(EOSIO#8060) EOSIO#8054: fix commas in ship abi
(EOSIO#8072) nodeos & keosd version reporting - 2.0
(EOSIO#8071) Update cleos to support new producer schedule - 2.0
(EOSIO#8070) don't rebuild llvm unnecessarily during pinned builds - 2.0
(EOSIO#8074) [2.0.x] Upgrade mac anka template to 10.14.6
(EOSIO#8076) Handle cases where version_* not specified in CMakeLists.txt - 2.0
(EOSIO#8088) [2.0.x] Linux build fleet update
(EOSIO#8091) report block extensions_type contents in RPC and eosio-blocklog tool - 2.0
(EOSIO#8105) Modify --print-default-config to exit with success - 2.0
(EOSIO#8113) [2.0.x] WASM Spec Test Step in CI
(EOSIO#8114) [2.0.x] Mac OSX steps need a min of 1 hour
(EOSIO#8127) [2.0.x] Move the ensure step into the build step, eliminating the need for templaters
(EOSIO#8144) fix pinned builds on fresh macOS install - 2.0
(EOSIO#8149) [2.0.x] CI platform directories
(EOSIO#8155) Post State history callback as medium priority - 2.0
(EOSIO#8173) ensure GMP is always dynamically linked - 2.0
(EOSIO#8175) [2.0.x] Unpinned and WASM test fixes
(EOSIO#8168) add harden flags to cicd & pinned builds - 2.0
(EOSIO#8180) [2.0.x] 10 second sleep to address heavy usage wait-network bug in Anka
(EOSIO#8192) Reduce logging - 2.0