Andreas

I just checked my configuration again (from docker-compose), and the aspect which made it not work in 4.8 and 4.9 was me setting `working_dir`, which was just some leftover configuration...

Yes, by not defining `working_dir`. If you define `working_dir` (to something other than the default), then it will not work, because phpmyadmin will be copied to that `working_dir` but Apache...

I experience this problem aswell - but I cannot easily downgrade my PHP version. How do you work around this problem? For now ApnsPHP just does not work as long...

I already did that - it does not work. The script is still permanently stuck.

No timeout seems to actually have an effect - without explicitely killing processes they are running forever, never stopping and all using 100% CPU. I have actually had a CPU...

That is what I did - I called the ini_set command at the very beginning of the script, before anything happens at all. Yet the cron script just goes to...

Nope, setting the stream_socket_client connect timeout does not work either - that's a connect timeout, so it should not have any effect on reading from a remote host anyway, as...

Not having a version number for this library is quite impractical - maybe it would be possible to version the releases? Using dev-master as a version is not good practice...

With the latest version a version number (v1.0.1) was added for packagist & composer. Thanks!

Still occurs in v3.1.9: ``` Uncaught Exception: Webmozart\Assert\InvalidArgumentException Expected an integer. Got: boolean Emitted in /psalm/vendor/webmozart/assert/src/Assert.php:2074 Stack trace in the forked worker: #0 /psalm/vendor/webmozart/assert/src/Assert.php(85): Webmozart\Assert\Assert::reportInvalidArgument() #1 /psalm/vendor/psalm/plugin-symfony/src/Handler/ConsoleHandler.php(266): Webmozart\Assert\Assert::integer() #2 /psalm/vendor/psalm/plugin-symfony/src/Handler/ConsoleHandler.php(245):...