Closed (fixed)
Project:
Upgrade Status
Version:
8.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Oct 2020 at 18:56 UTC
Updated:
18 Nov 2020 at 16:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mglamanRight here: https://git.drupalcode.org/project/upgrade_status/-/blob/8.x-3.x/src/Dep...
This could be conditionally skipped. If
\PHPStan\ExtensionInstaller\GeneratedConfigexists, don't execute this code.Comment #3
mglamanThis requires manual testing.
Before patch:
💥
Apply patch. No 💥, just report.
Comment #5
gábor hojtsyHm, we are running phpstan through exec() so whether that class exists in the runtime Drupal environment should not mean it does not need to be added to the phpstan config we run with exec()? This seems to be confirmed by the fail. I feel like I am missing something.
Comment #6
mglamanBut it's using the same configuration and autoloader. And the autoloader adds items to the configuration.
I'm really confused how this broke the tests when it fixed it manually. I'll do more investigations.
Comment #7
gábor hojtsyI sent this for a re-test. Apparently the fail case a month ago was on phpstan/phpstan 0.12.48, which falls in the range of https://github.com/mglaman/phpstan-drupal/issues/143. So that was a totally unrelated fail. It runs fine now :)
Comment #9
gábor hojtsyLanded, thanks again.