-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uopz seems to kill composer autoload #166
Comments
Do you have configured |
Thanks for the response. I didn't have I did wonder if this is a compatibility thing with xdebug, which the above dockerfile installs the latest 3.x version. I played around with this, installing down to 2.9.3. But unfortunately it presents the same error (with or without Yes I'm aware support for PHP 7 drops at version 7. Preparing for a PHP 8 upgrade now is what led us to uopz in the first place (replacing timecop with ClockMock in our tests). The plan was simply upgrade uopz when we got to PHP 8 and have this dependcy sorted ahead of time. |
Further info on this after playing with the docker setup over the last few days:
|
I think that requirement had actually been documented somewhere, but maybe this is no longer required for recent uopz versions. Anyway, it shouldn't harm to load the extension in that order.
The order in which the |
Is this still an issue with uopz 7.1.1? Note that at this point it wouldn't make sense to even attempt to fix uopz 6 (i.e. for support for PHP prior to 8.0.0). |
PHP: 7.4.30
uopz: 6.1.1
Hi. I'm using this package as a dependency of PHP MockClock. Uopz is installed in a php docker container using the following:
This actually worked at one point, and I think it has something to do with composer installs. But on multiple instances of this docker setup, we are seeing the following error on ANY page load:
Even if we manually follow that trace inside the container itself, the exact class and method it is complaining about being undefined, exist just fine. Also, if I remove
extension = uopz
from the php.ini for the container and rebuild it, all is fine without any other interaction with code.Any ideas?
The text was updated successfully, but these errors were encountered: