Skip to content

Commit

Permalink
Merge pull request #4575 from cuiweiyuan/develop
Browse files Browse the repository at this point in the history
chore: fix some comments
  • Loading branch information
chenyukang authored Aug 14, 2024
2 parents c35415f + b6b78b2 commit f4a3f7a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion network/src/tests/peer_registry.rs
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ fn test_accept_inbound_peer_eviction() {
peer.connected_time = now - Duration::from_secs(10);
};
}
// thoses peers will not be protect, we add them to evict_targets
// these peers will not be protect, we add them to evict_targets
for _ in 0..longest_connection_time_peers_count {
let peer_addr = peers_iter.next().unwrap();
let peer_id = extract_peer_id(peer_addr).unwrap();
Expand Down
2 changes: 1 addition & 1 deletion test/src/specs/sync/sync_churn.rs
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ impl Spec for SyncChurn {
let mining_node = select_random_node(&mut rng, &mut mining_nodes);
mining_node.mine(1);
// Because the test that waiting for nodes to sync has a implicit maximum waiting time
// (currently 60 seconds, we can sync about 200 blocks per second, so a maxium blocks of 10000 is reasonable)
// (currently 60 seconds, we can sync about 200 blocks per second, so a maximum blocks of 10000 is reasonable)
// and the implicit waiting time is not long enough when there are too many blocks to sync,
// so we stop mining when the tip block number is greater than 15000.
// Otherwise nodes may not be able to sync within the implicit waiting time.
Expand Down

0 comments on commit f4a3f7a

Please sign in to comment.