tari-project / tari / 14964897470

62%

Build Type

push

github

Committed by web-flow

Commit Message

feat: improve listening error propagation (#7050)

Description
---
Improved listening service error propagation if the peer manager returns
errors while checking if the peer is banned. This eliminates an
unnecessary panic when a peer is not found in the peer database.

Motivation and Context
---
All peer manager errors at this stage should not be treated as fatal
errors.

How Has This Been Tested?
---
System-level testing

What process can a PR reviewer use to test or verify this change?
---
Code review.

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Bug Fixes**
- Improved error handling when checking if a peer is banned, ensuring
non-critical errors do not interrupt normal operations and are logged as
warnings instead. Critical errors will still result in a fatal error.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Run Details

0 of 7 new or added lines in 1 file covered. (0.0%)

18 existing lines in 6 files now uncovered.

81803 of 111638 relevant lines covered (73.28%)

272542.59 hits per line