This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
(chainbase sync) print name of DB causing failure condition & win32 fixes #7657
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
heifner
previously approved these changes
Jul 16, 2019
heifner
suggested changes
Jul 16, 2019
|
Though what's interesting is that for the nodeos case those can never be hit because the exception is swallowed up in appbase's init |
heifner
approved these changes
Jul 17, 2019
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Change Description
Gets EOSIO/chainbase#48 & EOSIO/chainbase#49
EOSIO/chainbase#49 (print name of DB causing failure condition) may be a 1.8 candidate
Consensus Changes
API Changes
Documentation Additions