@dbu@phpc.social
@dbu@phpc.social avatar

dbu

@dbu@phpc.social

This profile is from a federated server and may be incomplete. Browse more on the original instance.

heiglandreas, to random
@heiglandreas@phpc.social avatar

The hanging bookshelf is shaping up quite nicely😁

A hang8ng bookshelf over a window

dbu,
@dbu@phpc.social avatar

@heiglandreas the view from the window looks amazing too 😍

heiglandreas, to random
@heiglandreas@phpc.social avatar

Great! Something changed in symfony/phpunit-bridge between 6.4.7 and 6.4.x-dev 15607a3 that now results in

Error in bootstrap script: PHPUnit\Event\Code\NoTestCaseObjectOnCallStackException:
Cannot find TestCase object on call stack

...

Not how I thought my day would start... 😕

dbu,
@dbu@phpc.social avatar

@heiglandreas the phpunit bridge is the one symfony component i really dont like and usually dont use at all.

dbu, to random
@dbu@phpc.social avatar

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?

PHPCSFixer, to random
@PHPCSFixer@phpc.social avatar

📢 NEW RELEASE!

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.

https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/releases/tag/v3.54.0

dbu,
@dbu@phpc.social avatar

@PHPCSFixer i needed last month 😅
Seriouspy though, thanks for the work, looking forward to use it in other applications

dbu, to random
@dbu@phpc.social avatar
dbu, to random
@dbu@phpc.social avatar

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

dbu,
@dbu@phpc.social avatar

@alessandrolai i do use the new event system with the ExecutionStarted event. looking into the event namespace https://github.com/sebastianbergmann/phpunit/tree/10.5/src/Event the only mention of "group" is the TestSuiteBuilder which builds an unused $group variable https://github.com/sebastianbergmann/phpunit/blob/10.5/src/Event/Value/TestSuite/TestSuiteBuilder.php#L34-L44

Skoop, to random
@Skoop@phpc.social avatar

TIL there is an #xrdebug project, which has nothing to do with either Extinction Rebellion or with xdebug 😂

dbu,
@dbu@phpc.social avatar
dbu, to drupal
@dbu@phpc.social avatar

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 !

heiglandreas, to random
@heiglandreas@phpc.social avatar

😂

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...

😂

It'S really fun to see what people use it for...

dbu,
@dbu@phpc.social avatar

@heiglandreas example.com? I am sure there is a bunch of security critical things being posted. And an incredible lot of random garbage

derickr, to random
@derickr@phpc.social avatar

On my way to chilly Montreal for #confoo, in style. With free Champagne courtesy of Air France. 🥂🇫🇷

#confoo2024

dbu,
@dbu@phpc.social avatar

@derickr on the other hand, the cold makes for a nice view.
Safe travels to you, looking forward to meet again!

heiglandreas, to php
@heiglandreas@phpc.social avatar

Ups!

Make sure you know what you do when using "finally" in #php

https://3v4l.org/hlh4m

dbu,
@dbu@phpc.social avatar

@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.

dbu,
@dbu@phpc.social avatar

@heiglandreas this one also illustrates that it is weird to return in finally: https://3v4l.org/LGjdC

dbu, to random
@dbu@phpc.social avatar

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!

The SFUGZH will do a meetup at the Liip offices in Zürich at Limmatstrasse 183 on Monday, 4. March 2024: https://www.meetup.com/de-DE/sfugzh/events/298479211/

Would be great to see you there! And please get in contact if you would like to do a presentation at the meetup.

dbu,
@dbu@phpc.social avatar

@Skoop next time hopefully!

dbu,
@dbu@phpc.social avatar

@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

Skoop, to random
@Skoop@phpc.social avatar

No @phptek for me this year. Everyone that is going, have fun!

dbu,
@dbu@phpc.social avatar

@Skoop @phptek same, the writing was on the wall 😢
There will always be another chance

dbu, to random
@dbu@phpc.social avatar

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

dbu,
@dbu@phpc.social avatar

@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.

dbu,
@dbu@phpc.social avatar
dbu,
@dbu@phpc.social avatar

@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

  • All
  • Subscribed
  • Moderated
  • Favorites
  • megavids
  • thenastyranch
  • rosin
  • GTA5RPClips
  • osvaldo12
  • love
  • Youngstown
  • slotface
  • khanakhh
  • everett
  • kavyap
  • mdbf
  • DreamBathrooms
  • ngwrru68w68
  • provamag3
  • magazineikmin
  • InstantRegret
  • normalnudes
  • tacticalgear
  • cubers
  • ethstaker
  • modclub
  • cisconetworking
  • Durango
  • anitta
  • Leos
  • tester
  • JUstTest
  • All magazines