- Ya
- 5 Septemba 2026, 00:18 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 391f7ba
SecurityService has been crash-looping on every new pod since the shared handoff store landed: "No default constructor found" for TerminalTicketRegistry, which fails the whole application context, so the rollout never completes and the service stays on its previous image. The class gained a second, package-private clock-injecting constructor for its tests. Spring only selects a constructor on its own when there is exactly one; with two and no annotation it looks for a no-arg default, which this class does not have. It got away with it before only because its public constructor happened to be no-arg.