Pascal Querner

@fballiano Changed some methods to visibility protected and fixed tests accordingly.

This is BC and I think its out of scope to fix that. It should be documented somewhere, yes but not further.

I think having 1 event as shown here is enough to even implement this new Error library or any library for that matter. I don't really see the need to...

My sentry implementation uses `controller_action_predispatch` to change the default error handler (cgi) and `default` for cli. (cron) The new event `core_app_init_environment_after` would make it more visible for cgi, I agree....

Imho this should be made optional. Our instance doesnt have images, instead they are coming from CDN anyways and we've overwritten the parts, but it would make it (I think)...

I'm also affected. `export DOCKER_BUILDKIT=0` does not work for me. ``` Docker version 26.1.1, build 4cf5afa Linux 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux...

``` $ docker compose build [+] Building 0.2s (11/19) docker:default => [vroom-cleanup internal] load build definition from Dockerfile 0.1s => => transferring dockerfile: 469B 0.0s => [symbolicator-cleanup internal] load build...

Okay, thanks for looking at it anyways. I'll try to replicate on other hardware. (Just wierd that its happening all of the sudden. Maybe some wierd docker update...)

For reference https://jira.readthedocs.io/en/master/examples.html#oauth

Its imagemagick. Where it gets its settings tho, that I don't know. I remember something from the TYPO3 days: https://stackoverflow.com/questions/18809692/why-do-imagemagick-based-thumbnail-images-of-pdf-files-in-typo3-have-black-backg https://forge.typo3.org/issues/37060 I dont know if that setting is available to...