I have to run a PHP application on Azure. There is a lot i hate about it, but one thing i really don't get. Sometimes (but not always) php-fpm says it is denied to read the /etc/php82/php-fpm.conf file. I found out that if i copy /usr/sbin/php-fpm82 to some different name, it suddenly works. I use https://github.com/eXistenZNL/Docker-Webstack/ 8.2 , which builds on alpine linux. I checked for apparmor but can't find any traces of it. I never observed the behaviour locally. Anybody got any ideas what is going on?
In v3.54 we introduce new fixer that should be really helpful for migrating PHPUnit's metadata (from annotations to native attributes) 😁. There are also several other fixes and internal improvements.
asking for some tech help: in the FOSHttpCache test listener, we start a PHP web server if needed. with phpunit 9, we checked the test suite for a specific group to know if we need to start it. i am moving to phpunit 10 but can't find how to detect the groups anymore: https://github.com/FriendsOfSymfony/FOSHttpCache/pull/565/files#r1538713152 #phpunit
I tailored my #varnish talk for the #drupal crowd, learning many interesting things about Drupal in the process.
I was positively surprised how much we talk the same language.
Hope to see you this weekend in Davos at #drupalmountaincamp !
One of my better ideas was registering a username on google as well as a domain of some term that users like to use when referencing some jane doe like person..
I use it in exactly that way. But many others do so as well...
@heiglandreas probably a risky pattern to return inside a try finally... I expected this, but on second thought it feels like php/java should forbid it. Then again reality could be more complicated where you only return under some condition and finally also only returns with conditions.
I guess return in finally is the offender.
Symfony is going strong, but there has been no Symfony User Group Zurich meetup in a looong time. Lets meet again and talk about Symfony, PHP and web technologies and have a drink together!
@Skoop sounds great. We hope to do the meetup again with some frequency.
It would be awesome if you are motivated to present something. We should be flexible to arrange it so the dates fit for you
I am trying to figure out what the right approach with the promise pattern is in regards to error handling. We have the HttpAsyncClient that on failure returns a rejected promise. Should it always return a promise or is it better to throw an exception and not go through the promise / call the onRejected callback when some unexpected error happens?
for context: https://github.com/php-http/promise/pull/31#pullrequestreview-1749296867
@heiglandreas sort of, yes. but from how i read the async client, the intention was to only handle http exceptions through the promise and always asap throw other exceptions as those are not part of the expected flow.
@heiglandreas if we have throwable, this could be an invalid type in a method parameter or similar static bugs. There is no value in passing those through the promise, things are just wrong when this happen and the dev should see it.
Same if the request can not be sent because of a setup error or such.
Imo promise is only for when a http request was attempted