Rb/dont wait for notifications 8.4 - #79
Merged
Merged
Conversation
(cherry picked from commit 22e378d)
* Don't wait for sending out notifications in update_node() and map_target() as server nodes only have a one second timeout before they consider registration failed. In some systems, apparently dumping the udp messages takes longer than that. * Improve send_notifications() to only do one db query, not multiple, and call broadcast_datagram() only once. * Improve notification trace logging (cherry picked from commit 966b08e)
rustybee42
force-pushed
the
rb/dont-wait-for-notifications-8.4
branch
from
August 14, 2026 07:34
4b49405 to
eb7449e
Compare
rustybee42
enabled auto-merge
August 14, 2026 07:42
philippfalk
approved these changes
Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.