Fix silent event loss in DomainParticipant status channel

src/dds/participant.rs

@@ -226,8 +226,12 @@ impl DomainParticipantBuilder {
     let (discovery_command_sender, discovery_command_receiver) =
       mio_channel::sync_channel::<DiscoveryCommand>(64);
 
-    // Channel used to report noteworthy events to DomainParticipant
-    let (status_sender, status_receiver) = sync_status_channel(16)?;
+    // Channel used to report noteworthy events to DomainParticipant.
+    // Capacity must be large enough to absorb the SEDP burst when multiple
+    // participants are discovered at once. A single participant can expose
+    // many endpoints (e.g. ~16 in a typical ROS 2 node), so 2048 handles
+    // large deployments without silent event loss.
+    let (status_sender, status_receiver) = sync_status_channel(2048)?;
 
     #[cfg(not(feature = "security"))]
     let security_plugins_handle = None;

src/dds/statusevents.rs

@@ -103,7 +103,7 @@ impl<T> StatusChannelSender<T> {
         Ok(())
       }
       Err(mio_channel::TrySendError::Full(_tt)) => {
-        trace!("StatusChannelSender cannot send new status changes, channel is full.");
+        warn!("StatusChannelSender cannot send new status changes, channel is full.");
         // It is perfectly normal to fail due to full channel, because
         // no-one is required to be listening to these.
         self.signal_sender.send(); // kick the receiver anyway