toto 0fca6e4e93 fix(correlation): Keep-Alive time window + orphan timer + TTL purge (v1.1.14) ...

Bug #1 - processSourceA: utilise bEventHasValidTTL en mode one_to_many
  au lieu de eventsMatch qui comparait les timestamps originaux. Apres ~10s
  les requetes A devenaient toutes orphelines alors que la session KA etait active.

Bug #4 - checkPendingOrphansForCorrelation: meme correction, cle identique
  = meme connexion en one_to_many, pas besoin de comparer les timestamps.

Bug #3 - cleanNetworkBufferByTTL: expiration B => emission immediate
  des pending orphans associes (ils ne peuvent plus jamais corréler).

Bug #2 - Orchestrateur: goroutine ticker 250ms appelle EmitPendingOrphans()
  pour drainer les orphans independamment du flux d'evenements entrants.
  EmitPendingOrphans() expose la methode comme publique thread-safe.

Tests: 4 nouveaux tests de non-regression (un par bug).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

2026-03-05 17:01:37 +01:00

..

correlated_log_test.go

refactor: remove unused code and fix documentation

2026-03-01 00:26:07 +01:00

correlated_log.go

fix: renforcer corrélation A/B et sorties stdout/fichier

2026-03-01 12:10:17 +01:00

correlation_service_test.go

fix(correlation): Keep-Alive time window + orphan timer + TTL purge (v1.1.14)

2026-03-05 17:01:37 +01:00

correlation_service.go

fix(correlation): Keep-Alive time window + orphan timer + TTL purge (v1.1.14)

2026-03-05 17:01:37 +01:00

event.go

fix(v1.1.13): socket ownership, correlation bugs, keepalive_seq

2026-03-05 16:03:13 +01:00