-
Notifications
You must be signed in to change notification settings - Fork 396
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
Update ORCA to alpha18. #3712
Update ORCA to alpha18. #3712
Conversation
Alpha17 out now, should also fix phpstan neon issues: https://github.com/acquia/orca/releases/tag/v1.0.0-alpha17 |
@TravisCarden do you have a timeline for releasing a new ORCA version that uses the shared Coding Standards library rather than ORCA's built-in standards? I think this will be necessary to get the static analysis tests passing here, since we developed to the shared standards rather than ORCA's (they are slightly different). |
@danepowell I'm working on a release as we speak. I'm hoping to get it out today. I'll let you know. |
All right, @danepowell. v1.0.0-alpha18, using our shared coding standards library, is out now! |
Just one final bug to squash before we can merge this. @TravisCarden I think ORCA is erroneously throwing a deprecation error here: https://travis-ci.com/acquia/blt/jobs/214613419#L2026 Notice that BLT uses symfony/config 3.4.29, and in that version the function BLT is calling is not deprecated, so I don't think ORCA should be throwing this error. This is just a guess, but I wonder if ORCA itself uses Symfony Config 4+ and that's why it's throwing an error (even though the SUT in this case uses Symfony Config 3). |
You're right, @danepowell: ORCA uses Symfony Config 4.3. I wonder if that constitutes a bug in phpstan. In any case, I'll see what I can do about it. |
I confirmed locally that if you use ORCA's phpstan binary, it causes this false positive. If you use BLT's phpstan binary, it works fine (even for the same version of phpstan). I think what's happening here is that phpstan is autoloading from its own directory, which means that it autoloads the wrong version of symfony for deprecation testing. You can confirm this by unceremoniously killing ORCA's symfony config: After that tests will pass. |
@danepowell I've worked around the issue in acquia/orca#33. I can't merge the change yet because it will cause my builds to fail until you unpin from diff --git a/.travis.yml b/.travis.yml
index ce2dc757..ba35f8ae 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -58,6 +58,7 @@ before_install:
# Install ORCA.
- git clone --branch ${ORCA_VERSION} --depth 1 https://github.com/acquia/orca.git ../orca
- curl https://patch-diff.githubusercontent.com/raw/acquia/orca/pull/30.patch | git -C ../orca apply
+ - curl https://patch-diff.githubusercontent.com/raw/acquia/orca/pull/33.patch | git -C ../orca apply
- ../orca/bin/travis/before_install.sh
install: My local testing indicates that you'll still have at least one problem to work out, but it works like before on the other packages I tested with, and I think based on that and the failure itself (see below) that the problem will have to be addressed in BLT. In other words, the ball is in your court. :)
|
0e0a5ce
to
7edc9e4
Compare
Upstream issue on the off-chance that there's some better way to work around this than to directly require |
https://github.com/acquia/orca/releases/tag/v1.0.0-alpha17
This is awesome because we should get full deprecation testing now.
Blocked by:
alpha17whatever version includes the librarymglaman/phpstan-drupal": "0.11.7"
introduced in Fixes #3738: Failing deprecation tests. #3739