This repository has been archived by the owner on Nov 15, 2021. It is now read-only.
Process SC events after write_batch() commit #426
Merged
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
added 2 commits
May 19, 2018 15:08
* Fixed a bug with smart contract events not being able to lookup the current block being processed due to the fact that the block persistence hasn't finalized via write_batch() commit. Events are now emitted after the commit, so that blocks can be looked up. fixes #424
|
Looks good, thanks for tracking the issue down! |
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.
What current issue(s) does this address, or what feature is it adding?
Fixes #424.
How did you solve this problem?
Emit SC events after the block batch has been committed.
How did you make sure your solution works?
Tested it.
Are there any special changes in the code that we should be aware of?
No.
Please check the following, if applicable:
make lint?make test?CHANGELOG.rst? (if not, please do)