ControllerConfig truncates DLedger peer addresses containing hyphens
Open
Beginner friendly
- Dominant language
- Java
- Stars
- 22.6k
- Forks
- 12k
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 27
Description
ControllerConfig.getDLedgerAddress splits each peer entry on every hyphen and returns only the second segment. A valid peer such as n0-controller-host:9878 is therefore resolved as controller instead of controller-host:9878. Expected behavior: split only between the peer id and its address.
Contributor guide
Research direction
Find ControllerConfig.getDLedgerAddress and trace how each peer entry is parsed. Reproduce the issue with n0-controller-host:9878, then add or update a focused test to confirm that only the separator between the peer id and address is used and the full address is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100