Skip to content
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

leverage get_range more #2259

Merged
merged 2 commits into from
Oct 18, 2024
Merged

leverage get_range more #2259

merged 2 commits into from
Oct 18, 2024

Conversation

joshuef
Copy link
Contributor

@joshuef joshuef commented Oct 17, 2024

No description provided.

@joshuef joshuef changed the title chore(networking): rename get_closest_peers -> get_close_group_closes… leverage get_range more Oct 17, 2024
@joshuef joshuef marked this pull request as ready for review October 17, 2024 06:39
}

debug!(
"Network knowledge of closest peers in range of {key:?} are: {:?}",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the log better to be :
Network knowledge of closest peers in range of {:?} to target {key:?} are: {:?}, expected_range.log2(), restricted_closest_peers.len()

This should allow us to return more peers for various network operations, and leverage
range based gets more frequently
@joshuef joshuef enabled auto-merge October 18, 2024 03:25
@joshuef joshuef added this pull request to the merge queue Oct 18, 2024
Merged via the queue into maidsafe:main with commit 84324eb Oct 18, 2024
26 checks passed
@joshuef joshuef deleted the Feat-CloseInRange branch October 18, 2024 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants