forked from tronprotocol/java-tron
-
Notifications
You must be signed in to change notification settings - Fork 1
feat(db): support solidity conditional shutdown #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
317787106
wants to merge
7
commits into
develop
Choose a base branch
from
feature/solidity_shutdown
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
4101be4
support shutdown for SolidityNode
317787106 8895b7b
disable p2p
317787106 62107e6
optimize pushVerifiedBlock
317787106 0e5a48f
use flag in getBlockByNum, getLastSolidityBlockNum
317787106 18cbc16
delete invalid testcase
317787106 50c76de
format the code
317787106 1e9c558
add InterruptedException for processSolidityBlock
317787106 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[MUST] hitDown path leaves callers writing a fake success
When
latestSolidityNumShutDownis hit,processBlockflipshitDown=true, unparks the hit-thread, and returns normally. The callerSolidityNode.loopProcessBlocktreats that as success, then executessaveLatestSolidifiedBlockNum(blockNum)and logs"Success to process block", while the block was never actually pushed into BlockStore. Depending on the race between the hit-thread'sSystem.exit(0)and the current thread's save,LATEST_SOLIDIFIED_BLOCK_NUMmay be advanced to a block number that does not exist in the store — producing an inconsistent DB state and misleading logs.Suggestion: Throw a dedicated sentinel (e.g.
P2pExceptionwith a new TypeEnum, or aHitDownException) fromprocessBlockwhen entering the hitDown branch, and letloopProcessBlockbreak out without callingsaveLatestSolidifiedBlockNum. Alternatively, let the caller checktronNetDelegate.isHitDown()before writing state.