Jason Woods
Jason Woods
@mortenson Before I do any PR I just wondered if you had any ideas why it might not have been working without this? Specifically, inside the Symfony Plugin it automatically...
> It seems logical that we may need to copy more from that codebase, which is sounds like you did in testing. This is the "hardcoded" line in the Symfony...
Just wanted to track here that Amazon seem to not support EPEL-like repositories anymore so it might cause some issues if there is every a packaging problem if you're using...
Reproduction case in #42 reproduces this every time.
It's looking like the `$policy`, `$pool` and `$request` don't exist at the moment in Composer 2 so perhaps this is now much easier to implement?
Having this problem where the UI just gets squashed on small size screens. I'm usually able to zoom such apps so would be great to restore this. It's not just...
Is it worth defining the modules path in the layer so there’s one less step? I think most places referencing enabling the legacy providers document the conf environment but not...
OpenSSL builds the legacy provider by default so in a way this provider is usually distributed in most operating systems that provide it and is kind of already being built...
@mnapoli It could be. I only mention libxml because of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280775. Usually php-fpm would disable SIGPIPE, but I've found sources showing there's been things in past where libraries re-enable it...
I can try and test with https://github.com/brefphp/aws-lambda-layers/pull/199 once it is released.