Repository navigation
fix(jsonrpc): normalize error responses and fatal handling #6985
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
Merged
lvs0075
merged 1 commit into
tronprotocol:release_v4.8.3
from
waynercheung:feat/jsonrpc-error-sanitization
Oct 12, 2026
+3,104
−319
Merged
Changes from all commits
Commits
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
97 changes: 0 additions & 97 deletions
97
framework/src/main/java/org/tron/core/services/filter/CachedBodyRequestWrapper.java
This file was deleted.
Oops, something went wrong.
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.
[NIT]
findFatalCauseandExitManager.findTronErrorboth walk a cause chain but guard against cycles differently (two-pointer here, aHashSetthere). Not a problem by itself. If you want one convention, a shared walker incommonnext toExitManagercould serve both, or, if a depth cap were acceptable, a plain bounded loop would read more simply than the two-check-per-step form.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.
Thanks. I'd keep the current scan in this PR for two reasons:
resolveError, including mapped exceptions, and may encounter anOutOfMemoryError. The two-pointer approach avoids allocating a visited set.A shared allocation-free walker in
commonmakes sense as a separate refactor. It should preserve each caller's matching rule: onlyTronErrorforExitManager, and the four fatal categories for JSON-RPC.findTronErroralso servesExecutorServiceManager,Manager,DposTask, and the default uncaught exception handler, so the refactor needs validation across those paths. I'll include it as an optional refactoring item in the process-level fatal-handling follow-up.