-
Notifications
You must be signed in to change notification settings - Fork 70
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
Spam in debug.log file #94
Comments
@indykoning can you confirm this? |
I do also experience this on version 2.6.1 |
Same here on Magento 2.4.4 and and 2.3.7. |
Same here 2.4.4 |
See my response here #79 (comment) This probably works #79 (comment) however it makes no sense that that should happen and that it does not happen for other people. |
I have the same experience on 2.4.5-p1 |
We've done some more digging and sadly we're completely unable to fix this from our side. The log spam should not cause any problems though. Because of Magento's automatic Factory generation while developer mode is active it will try to generate factories for classes that don't exist, for packages that don't exist if you try to call class_exists Magento tries to generate the class when you call it using the folowing function: Which fails and throws an exception. It's all because of quirks and "features" of Magento's code and factory generation not playing too nice with class_exists. |
The only ways to really fix these messages in all environments is using the patch described here: #79 (comment) |
I am experiencing a log spam in debug.log - magento 2.4.4 and php8.1:
when i remove the sentry config from the .env then the logs disappear...
The text was updated successfully, but these errors were encountered: