The issue is caused by the call to ReadonlyMode::setReason in finalSetup, which happens before the service locator is ready.
It then proceeds to spam this deprecation message 13 more times. If stack traces are shown, that is ~700 lines of nonsense.
The issue is caused by the call to ReadonlyMode::setReason in finalSetup, which happens before the service locator is ready.
It then proceeds to spam this deprecation message 13 more times. If stack traces are shown, that is ~700 lines of nonsense.