• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tari-project / tari / 18936078418
62%

Build:
DEFAULT BRANCH: development
Ran 30 Oct 2025 10:38AM UTC
Jobs 1
Files 700
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

30 Oct 2025 09:24AM UTC coverage: 59.648% (+0.1%) from 59.547%
18936078418

push

github

web-flow
fix: multi_address_with_stats merging to only retain the newest valid claims in the peer_db (#7535)

Description
---
The peer_db now only retains the latest claims, and peer multi-address
merges cleans out old data.

Closes #7491.

Motivation and Context
---
See #7491.

How Has This Been Tested?
---
Added new unit tests:
- MultiAddressWithStats
  - `fn it_merges_addresses_with_stats_correctly()`
  - `fn it_merges_when_config_overlaps()`
  - `fn it_prefers_advertised_addresses_over_config_on_tie()`
- PeerManager
  - `async fn it_correctly_merges_old_and_new_address_claims()`

System-level testing.

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

<!-- 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

- New Features
- Claim-aware peer address merging that prefers newer signed claims,
preserves configured addresses, enforces capacity limits, and
deterministically breaks ties in favor of advertised addresses.
- Batch-style address updates with automatic pruning of stale addresses
to keep peers’ address lists current.

- Bug Fixes
- Eliminates inconsistent ordering, duplicates, and outdated addresses
after updates; preserves and propagates usage/latency stats correctly.

- Documentation
  - Clarified merge, replacement, and tie-breaking behavior.

- Tests
- Added tests for claim timestamps, m... (continued)

344 of 353 new or added lines in 7 files covered. (97.45%)

9 existing lines in 4 files now uncovered.

67926 of 113879 relevant lines covered (59.65%)

302582.71 hits per line

New Missed Lines in Diff

Lines Coverage ∆ File
4
88.47
1.04% comms/core/src/peer_manager/manager.rs
5
91.75
2.09% comms/core/src/net_address/mutliaddresses_with_stats.rs

Uncovered Existing Lines

Lines Coverage ∆ File
1
87.11
0.84% comms/core/src/net_address/multiaddr_with_stats.rs
1
61.57
2.1% comms/dht/src/connectivity/mod.rs
2
55.76
0.0% comms/core/src/connectivity/manager.rs
5
77.66
-1.02% comms/core/src/connection_manager/dialer.rs
Jobs
ID Job ID Ran Files Coverage
1 18936078418.1 30 Oct 2025 10:38AM UTC 700
59.65
GitHub Action Run
Source Files on build 18936078418
  • Tree
  • List 700
  • Changed 14
  • Source Changed 7
  • Coverage Changed 12
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #18936078418
  • efd8ae68 on github
  • Prev Build on development (#18934144103)
  • Next Build on development (#18940334899)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc