Manuel Munz

The fork from @koehnlein works fine for me with guzzle 7.5.0

I recently also stumbled upon that issue and it is currently present in many test setups for TYPO3 and it's extensions. E.g. here: https://github.com/TYPO3/styleguide/blob/3baee32b70d60fe13741435597053c240ccc3463/Build/testing-docker/docker-compose.yml#L294 The lines ``` XDEBUG_MODE=\"off\" \ bin/phpunit...

@ndeloof while i tend to agree, it is imho still a problem that docker-compose v1 and v2 parse these scripts differently.

I tested this with TYPO3 12.4.20 and works fine. Finally correct image dimensions after upload and much quieter logs. Thanks!

@weakbit i finally found some time and motivation to test this. In the meantime we cleaned up the s3 storage, so only about half of the files is left compared...

@MohsinQK thanks, but i don't have such a folder. Just many files in the root of the bucket and 5 folders.

@weakbit i've now tested feature/performance-improvements-caching: - without the feature/performance-improvements-caching branch i still get the OOM error - with the improvements branch: no OOM, but the request to /typo3/ajax/filestorage/tree/filterData?token=xxx&q=searchWord times out...

@Lagerregal the search result is loading now with 512M memory limit. It is still not fast (80s), but the OOM is gone.

@tyler36 i created a ddev test setup here: https://github.com/mmunz/browsersynctest/tree/multiple-domain-support It is a ddev setup with an additional hostname and two docroots. To test it do: * checkout the test project...

@tyler36 i have to look deeper into this, but i suspect this is same strange caching issue (browser cache or even the http-proxy-middleware).