- Ya
- 14 Agosti 2026, 01:26 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 0237c36
LegalPendingCountPublisher takes its NATS Connection as required=false and returns quietly when it is null. The shared NatsConfig is **************** and this ConfigMap had no nats: block at all, so the bean never existed and every pending-count update was dropped at the null guard, at DEBUG. Live pod confirms it: [LegalCount] Initialized (nats=false) MediaService's relay has been up and subscribed to legal.packages.> the whole time, waiting for frames nobody published. The badge therefore only moved when the browser re-seeded over REST — on mount, on socket reconnect, or on its 60-second net — which is why a member had to refresh to discover a package waiting for them. JetStream stays off, as a literal so no environment can flip it: @ComponentScan("com.kamo") already pulls in the shared WebhookDeliveryWorker, which starts as soon as a Connection AND a JetStream bean both exist and then binds the durable 'los-pipeline-webhook-worker' on LOS_PIPELINE. That durable is SecurityService's, and a second binder competes for its messages rather than duplicating them. The badge subject is unstreamed by design anyway. Guarded by **************** which fails on a ConfigMap that omits nats.enabled or turns JetStream on.