Skip to content

Conversation

@davecgh
Copy link
Member

@davecgh davecgh commented Jun 14, 2025

This modifies the logic that determines if a mixing message should be requested to avoid requesting recently removed mixing messages by making use of the newer RecentMessage method that queries both the existing messages in the mixing pool and recently removed messages.

@davecgh davecgh added this to the 2.1.0 milestone Jun 14, 2025
@davecgh davecgh closed this Jun 16, 2025
@davecgh davecgh force-pushed the netsync_no_reqs_for_recently_removed_mix_msgs branch from 5467d4d to 47d690d Compare June 16, 2025 15:48
@davecgh
Copy link
Member Author

davecgh commented Jun 16, 2025

This was actually merged. I had a rebase mishap.

47d690d

@davecgh davecgh deleted the netsync_no_reqs_for_recently_removed_mix_msgs branch July 2, 2025 08:47
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