fixed issue on udpstreamer trigger logic

Common/Client/go/wshub/ringbuf.go

@@ -221,6 +221,19 @@ func ringCoverage(bucket, capacity int) int {
 	return capacity / 2 * bucket
 }
 
+// captureLagSec is how much further back than the window itself a ring has to
+// reach to deliver a capture of it.
+//
+// A capture is not read out when its last sample arrives but captureMarginSec
+// later, and then only on the next push tick — so by the time the window is
+// extracted, its oldest sample is that much deeper in the ring. A ring holding
+// exactly the window has already overwritten the front of its own capture, which
+// is what made every shot at a short window come back missing its head. The
+// pre/post split does not enter into it: the harvest is a post-window after the
+// trigger and the read reaches a pre-window before it, so the two sum to the
+// window whatever the split.
+const captureLagSec = captureMarginSec + 1.0/30.0
+
 // activeWindowSec is the timespan the buffers must cover. An armed trigger owns
 // it: its pre-window has to already be in the ring when the trigger fires or
 // there is nothing to back-fill the capture from. Otherwise it is the widest
@@ -228,7 +241,7 @@ func ringCoverage(bucket, capacity int) int {
 func (h *Hub) activeWindowSec() float64 {
 	if h.trigger != nil && h.trigger.Active() {
 		if cfg := h.trigger.Config(); cfg.windowSec > 0 {
-			return cfg.windowSec
+			return cfg.windowSec + captureLagSec
 		}
 	}
 	widest := 0.0