-
Notifications
You must be signed in to change notification settings - Fork 60
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
[v9.17.0.300] [workaround found] ErrorException: Warning: PDOStatement::bindParam(): Argument #2 ($var) must be passed by reference, value given #143
Comments
If you set |
@ruudk Thanks for the detailed issue report and for the information on the workaround! It really helps narrow down where the problem may be. We are working on reproducing this locally. |
I was able to reproduce the problem. I have a work in progress PR exploring the best way to fix this as it touches on a PHP 8 API change that impacts other parts of the code. What we do here will establish the pattern we need to follow in future similar scenarios. My first attempt looks to have been too general so it will need to be reworked. |
The revised fix (with automated test) has been merged. It will be in the next release. |
Hi all, We just put out a patch release (9.17.1) that addresses this issue! We'll leave this issue open for a few days to verify that this solution is working well for folks, so please feel free to leave any feedback about your experience! Thanks! |
Deployed 9.17.1.301 to production and enabled the Explain Tracer again. It works 🎉 Thanks. |
Description
I just deployed the latest agent on PHP 8.0.3 and am getting this exception that I cannot explain:
My first thought was that this is related to Doctrine DBAL/ORM but then I searched for
bindParam
in the agent code and found:newrelic-php-agent/agent/php_pdo.c
Lines 110 to 123 in adbdca6
Could it be related to this?
The Doctrine code passes it correctly via reference.
Your Environment
Ubuntu PHP 8.0.3
Additional context
I'm using the latest Doctrine DBAL/ORM:
The text was updated successfully, but these errors were encountered: