-
Notifications
You must be signed in to change notification settings - Fork 1.7k
refactor(config,protocol,ci): optimize config binding #6762
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
kuny0707
merged 11 commits into
tronprotocol:release_v4.8.2
from
317787106:hotfix/optimize_binding
May 14, 2026
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
bd989fa
optimze binding
317787106 e575b7f
Merge branch 'release_v4.8.2' into hotfix/optimize_binding
317787106 b70fccc
prune proto
317787106 953651d
optimize external.ip
317787106 99dcd91
optimize trustNodeAddr
317787106 e15cbbf
fix the bug of VmConfigTest
317787106 16494de
remove the comment of trustNode in config
317787106 b225467
delete withoutPath(topicDefaults) for EventConfig
317787106 84775df
update the comment of constantCallTimeoutMs
317787106 59ea298
update testcase
317787106 10eb9f0
update EventConfigTest
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 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
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.
[NIT] normalizeNonStandardKeys cleanliness: withoutPath + hasPath guard
Two small cleanups apply to both
CommitteeConfig.normalizeNonStandardKeys(this file, allowPBFT/pBFTExpireNum) and the siblingNodeConfig.normalizeNonStandardKeys(isOpenFullTcpDisconnect / discovery.external.ip):section.withValue(newKey, ...)adds the new key but does not remove the legacy one. After normalize, both keys coexist in the Config tree. This is harmless forConfigBeanFactory(only the canonical name binds), but any downstream diagnostic that walks the raw Config (debug dumps, future read paths) will see two competing entries with no documented winner. Chaining.withoutPath(oldPath)after the rename keeps the post-normalize tree canonical.NodeConfig.normalizeNonStandardKeyscallssection.getIsNull("discovery.external.ip"), which throwsConfigException.Missingif the path itself is absent (it only returns true when the path exists with a null value). The current code relies on thereference.confdefault atexternal.ip = ""always populating this path. If a user explicitly writesnode.discovery = nullornode.discovery.external = nullto disable a sub-tree, normalize blows up with a stack trace pointing into its internals rather than at the offending config path. AhasPathguard or an explicit javadoc precondition (sectionmust be merged with reference.conf fallback) makes the implicit contract traceable.Neither is a correctness bug given current
reference.confcontent; treat as nits.