-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
duplicate stubs error #466
Comments
@staabm since the PdoStatement.stub is now in phpstan-src merged + released, it needs to be removed here, too, right? |
It doesn't work yet with stubs from phpstan-src only. I don't know yet how we can make this error go away. If you got this error, you can proceed like usual. It is reported only when no result cache exists. As soon as the result cache is generated the error no longer happens |
since we have loaded bleedingEdge.neon I (for now) disabled the feature that detects doubles: parameters:
featureToggles:
duplicateStubs: false # workaround for: https://github.com/staabm/phpstan-dba/issues/466 in the CI it will fail all the time, cause the result cache isnt existing |
Ondrej sounds like, that there will be no fix. Duplicate stubs are not allowed, when they are in phpstan-src :/ |
You should enable the result cache in CI. It saves a lot of time. e.g. with GithubActions you can use actions/cache to persist the cache between build jobs |
fixed in upcoming 2.x release |
@glaubinix I did some major internal refactorings in the main branch for the upcoming PHPStan 2.x release. could you double check against your composer app-repos whether I did not broke something for you? |
@staabm I will have a look but can only do so when I am back at work on Monday |
@staabm tried |
awesome - thanks for reporting back |
need to figure out a way how we can handle these stub errors and test whether we still need these stub files after all
phpstan/phpstan#8378
I cannot reproduce it yet or know the exact circumstances, but I sometimes get errors like
The text was updated successfully, but these errors were encountered: