Internal error: Class staabm\PHPStanDba\Tests\Fixture\PreparedStatement was not found

[evomase]

The changes made in this PR #755 have caused a new issue. I had to revert that change locally to fix the issue below.

Internal error: Class staabm\PHPStanDba\Tests\Fixture\PreparedStatement was not found while trying to analyse it - discovering symbols is probably not configured properly. while analysing file /home/runner/work/src/helpers.php
Post the following stack trace to https://github.com/phpstan/phpstan/issues/new?template=Bug_report.yaml: 
## phar:///home/runner/work/vendor/phpstan/phpstan/phpstan.phar/src/Reflection/BetterReflection/BetterReflectionProvider.php(144)
#0 phar:///home/runner/work/vendor/phpstan/phpstan/phpstan.phar/src/Reflection/ReflectionProvider/MemoizingReflectionProvider.php(40): PHPStan\Reflection\BetterReflection\BetterReflectionProvider->getClass()
#1 /home/runner/work/vendor/staabm/phpstan-dba/src/Rules/SyntaxErrorInPreparedStatementMethodRule.php(81):

[staabm]

//cc @bnowak can you have a look?

[staabm]

Thanks for reporting

@evomase can you give us a small/recuced reproducer for the problem?

[bnowak]

I was able to reproduce it in my project with my default config, so it looks like general error now on main branch.
@staabm if that's an issue (I guess yes), please revert my PR and I'll take a look closer on that in a few days (I hope will find time).

So far, I noticed that this class PreparedStatement is injected into SyntaxErrorInPreparedStatementMethodRule as argument, and I assume it shouldn't as it comes from tests (so shouldn't be used in runtime environment). I don't have detailed knowledge (yet) about phpstan internals, but happy to investigate it closer when will find time 😉

@evomase I'm sorry for troubles regarding that.

[staabm]

no worries. thanks for the hint which gave me an idea how to fix it / what the root cause could be.

[staabm]

please try the latest dev-master version which includes a fix.

I have a feeling that this might also affect pdo/mysqli/doctrine support in a similar way.. it might mean you need to enable pdo/mysqli both togehter even if you only want to use only one of them. I did not verify this thesis atm though

[bnowak]

@staabm Thanks for so quick response, errors I had previously disappeared.

However, now I have another similar one:

Internal error: Class Dibi\Connection was not found while trying to analyse it - discovering symbols is probably not configured properly. while analysing file                                              
/opt/workbuzz/report-service/tests/Reports/Suites/Integration/Infrastructure/Service/Filesystem/FlysystemJsonFilesStorageTest.php                                                                           
Post the following stack trace to https://github.com/phpstan/phpstan/issues/new?template=Bug_report.yaml:                                                                                                   
## phar:///opt/workbuzz/report-service/vendor/phpstan/phpstan/phpstan.phar/src/Reflection/BetterReflection/BetterReflectionProvider.php(144)                                                                
#0 phar:///opt/workbuzz/report-service/vendor/phpstan/phpstan/phpstan.phar/src/Reflection/ReflectionProvider/MemoizingReflectionProvider.php(40):                                                           
PHPStan\Reflection\BetterReflection\BetterReflectionProvider->getClass('Dibi\\Connection')                                                                                                                  
#1 /opt/workbuzz/report-service/vendor/staabm/phpstan-dba/src/Rules/SyntaxErrorInDibiPreparedStatementMethodRule.php(83):                                                                                   
PHPStan\Reflection\ReflectionProvider\MemoizingReflectionProvider->getClass('Dibi\\Connection')                                                                                                             

Is it connected with enabling pdo/mysqli? It doesn't look so

[staabm]

another useful stacktrace, thanks.

fixed with #758

[bnowak]

I can confirm that now everything work fine with main branch.

Thanks for so ultra quick fixes, you're a star 👍💪

In fact, I should add hasClass() checks from very beginning in my PR 😅 my fault - lesson learnt 😄

[staabm]

Awesome. Thanks