-
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
Drush fatal error with various commands -- looking for Drupal 8 RfcLogLevel #182
Comments
@jenlampton do you have
I just tried on a vanilla Backdrop I just enabled So we still need STR to get moving on this issue. |
When I get this error, it's running drush_watchdog_severity_levels() from the Drush phar code, not the version that is in .drush/commands/backdrop/. This is Drush 8.1.15. update: ah, no, it's earlier. Drush 8 implements system_watchdog(), which gets called by any watchdog() error, and it is apparently not playing well with Backdrop. |
@serundeputy I found that I was still on the @bradbulger check your drush branch, are you on (going to close this issue -- @bradbulger please re-open if needed!) |
Weirdly I'm seeing the same error under different circumstances, with just one site in just one environment:
In the environment where this happens I'm running Backdrop 1.13.2, Drush 8.2.3, and the latest commit in branch The identical site (same exact codebase) in a different environment using PHP 7.3 does not experience this error using the same versions of Drush and the Drush Backdrop commands. And other Backdrop sites in the same environment as the one with the problem do not experience the same error. For the life of me I can't figure out what's going on here! |
Now I see I get the same error on a different site in the same environment. On this site
But then look what happens when I immediately run this series of commands after that:
So...in some cases this problem comes and goes, but when it does happen, it's a fatal error? |
@jackaponte check the drush branch, or if you have any patches applied. Maybe delete / replace drush where you are seeing the error, just to be sure? |
I'm using Drush 8.2.3 with no patches applied; I'm on the 1.x-1.x branch of the Backdrop commands, with commit But as I noted before, the problem comes and goes, fairly inscrutably. When I started writing this update, |
I am not running drush from checked out code. I'm not entirely sure how to do that. This is my global Drush installation in /usr/local/bin/drush that's running a drush.phar file. The version is 8.1.15. (The "drush version" command does not work in a Backdrop context btw.) It is loading system_watchdog() from phar:///usr/local/bin/drush.phar/includes/drupal.inc and that causes the attempt to run Drupal 8 code (or whatever the reference to RfcLogLevel is). If it only does this sometimes, then the question is, when does it include that file? |
@bradbulger Have you tried installing a fresh copy of the Drush Backdrop commands and seeing whether the issue persists for you? You can download the most recent 1.x-1.x release via this link: https://github.com/backdrop-contrib/drush/archive/1.x-1.x.zip |
Some observations in case they jog anyone's memory: backdrop_pm_enable.drush.inc is the only Backdrop Drush file I can find that includes The error refers to
That function is replaced in backdrop/includes/environment.inc. But maybe, on some sites, something is causing Drush to not properly detect that Backdrop is being used, causing the Drupal version of the function to be used instead? |
Welp, not long later I tried disabling then re-enabling |
FWIW, I just encountered this same error, and disabling civicrm made it go away. (Though re-enabling civicrm brought it back.) |
Strange, I am using drush on a number of sites that run civicrm and am not seeing this. Which command in particular causes the error, @bugfolder? |
It was drush dis, also drush pmu. |
I confirm both
|
I'm testing PHP 8 with backdrop-drush. I get this error in PHP 8 but not in PHP 7.4 (when running Things have likely moved around a bit so the error is in
|
I'm seeing the following while attempting
drush updb -y
The text was updated successfully, but these errors were encountered: