- Ya
- 11 Agosti 2026, 04:49 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 430e97d
StorageQuotaService took its five repositories as required constructor arguments. Services in this estate component-scan com.kamo with a wildcard but declare an EXPLICIT @EnableJpaRepositories package list, so a new @Service in this library is picked up everywhere while its repositories exist only where those packages happen to be listed. The result was "Consider defining a bean of type OrgStorageSnapshotRepository" and a crash loop in MediaService, AIService, ConversionService, DocsService, ESigService, KBService and MCPGatewayService the moment each one rebuilt — chat included, because MediaService serves it. The repositories are now ObjectProvider-injected and quotaFor returns unlimited when they are absent. That matches the intent already documented on ImageService, where the quota service itself is optional: a service that cannot see the billing tables does not enforce a ceiling, exactly as one with no quota bean does. It never prevents startup. The estate's own KamoInitializer notes warn about precisely this trap. I added the bean without applying it.