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
Internal error: Property $_bezeichnung was not found in reflection of class Application_Model_Artgroesse #6944
Comments
This bug report is missing a link to reproduction on phpstan.org. It will most likely be closed after manual review. |
the error does not occur with 1.5.1, only with 1.5.2 |
Can you please create a small reproducing repository that shows this problem? Looks like somehow traits are involved. Thanks. |
we are not yet able to reproduce the error locally. only happens in github actions. need to investigate. |
I've create a way to reproduce the same issue with a class method instead of a class property here: https://github.com/zacharylund/phpstan-dup-class-poc I'm pretty sure this has to do with legacy code with (non-namespaced) duplicated class names in different directories. I see this in my CI environment as well, and it was hard to reproduce locally until I set the maximum number of processes to 1, which is how it runs in CI. I suspect multiple processes on a large repo means the duplicated class names don't get analyzed in the same process and therefore don't fail. I think the issue is this line: phpstan/phpstan-src@22f755c#diff-3887df0457831e1b8fd86144e1d07a7737643885122108493625853be7f4a198R1135 Description was previously assigned as:
Now it is assigned as:
Reverting this line fixes the error in my example repo. This also appears to be cache related because running PHPStan 1.5.1 works, upgrading to 1.5.2 works until you clear cache and then 1.5.2 fails. |
Thanks for this great investigation. We also had the impression that its cache related.. maybe 1.5.2 also misses a cache-key change and therefore the error only happens after clearing it manually? |
Fixed: phpstan/phpstan-src@81abfb4 + 970a7f0 |
Thank you for fixing. It was a blocker for us, and I did not yet have an idea on how to fix it |
Thank you! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug report
not sure this is related to 1.5.1 or 1.5.2 but maybe the exception trace rings a bell
The text was updated successfully, but these errors were encountered: