fet(event): optimize event service to obtain transaction information #6443
+94
−41
Conversation
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
0xbigapple
reviewed
Sep 12, 2025
| endNum = manager.getDynamicPropertiesStore().getLatestSolidifiedBlockNum(); | ||
| } | ||
| initEventService(manager.getChainBaseManager().getBlockIdByNum(endNum)); | ||
| long startNum = endNum == 0 ? 0 : endNum - 1; |
There was a problem hiding this comment.
If now solidifiedBlockNum is 100, but the startSyncBlockNum in config is 1000, it still start writing events from 99?
Contributor
There was a problem hiding this comment.
Will write from 100, and you need to configure startSyncBlockNum reasonably.
0xbigapple
approved these changes
Sep 15, 2025
lvs0075
approved these changes
Sep 15, 2025
| for (int i = 0; i < block.getTransactions().size(); i++) { | ||
| Protocol.Transaction tx = block.getInstance().getTransactions(i); | ||
| Protocol.TransactionInfo txInfo = result.getInstance().getTransactioninfo(i); | ||
| Protocol.TransactionInfo txInfo = list.getTransactionInfo(i); |
Contributor
There was a problem hiding this comment.
if list get from getTransactionInfoByBlockNum is empty, or list.getTransactionInfoCount() != block.getTransactions().size(), is there any problem?
Contributor
There was a problem hiding this comment.
No problem, this situation does not exist, otherwise the data is inconsistent.
kuny0707
approved these changes
Sep 15, 2025
halibobo1205
pushed a commit
to halibobo1205/java-tron
that referenced
this pull request
Oct 14, 2025
…ronprotocol#6443) * feat(event): solve the problem of concurrent access to a single SR * feat(event): solve the concurrency problem of single SR obtaining solid ID
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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 does this PR do?
Optimize event service to obtain transaction information.
Why are these changes required?
This PR has been tested by:
Follow up
Extra details