lifeweaver

I miss Logback configuration via Groovy too, but I switched over to configuring in a Groovy class, and it's not too bad. It's certainly better than XML in my opinion.

https://logback.qos.ch/manual/configuration.html, see # 3 about the 'service-provider loading facility'. Then you can just configure your logging via a class implementing the logback Configurator class. Note this link was useful(Part about...

I understand runtime log configuration is a feature many use, in my situation I couldn't wait. As for the rationale, the Logback team made the decision, I don't like it...

As a work around until/if it gets implemented you could try something like what enzo did on this [question](http://stackoverflow.com/questions/36072320/grails-3-csrf-protection).

> @lifeweaver, thanks for this: > > > Then you can just configure your logging via a class implementing the logback Configurator class > > I got Configurator code working,...

I had this same issue. See https://github.com/darrachequesne/spring-data-jpa-datatables-sample/issues/2 I'll note that for me I had tried adding the @EnableJpRepositories annotation, but I kept getting the same error. But once I removed...

Note: WidgetService.java:365 might need similar treatment, but I didn't change it as I don't know how to test that part.

I'll see if I can do a pull request. This was on Android 12, Pixel 6 Pro.

I believe the problem image is https://preview.redd.it/z98ymspt53c81.png?width=320&crop=smart&auto=webp&s=a63c50872c139dafe0739c29bf8a6281ac22bb22

I was able to get the image to load by following: https://developer.android.com/topic/performance/graphics/load-bitmap and setting the reqWidth to 2048, and the reqHeight to 1080. That made sure the image was small...