ArgumentCountError in FeaturesInstallStorage::__construct()

Created on 6 June 2023, over 1 year ago
Updated 20 June 2023, over 1 year ago

Problem/Motivation

Running drush feature-revert throws this error:

[error] ArgumentCountError: Too few arguments to function Drupal\features\FeaturesInstallStorage::__construct(), 1 passed in /app/core/lib/Drupal/Component/DependencyInjection/Container.php on line 262 and at least 2 expected in Drupal\features\FeaturesInstallStorage->__construct() (line 54 of /app/modules/contrib/features/src/FeaturesInstallStorage.php) #0 /app/core/lib/Drupal/Component/DependencyInjection/Container.php(262): Drupal\features\FeaturesInstallStorage->__construct(Object(Drupal\Core\Config\CachedStorage))

Steps to reproduce

Run : drush fr somefeature -y, or drush fra -y

haven't been able to look into what might be causing it, I've reverted back to 3.11 for the time being.

πŸ› Bug report
Status

Closed: works as designed

Version

3.13

Component

Code

Created by

πŸ‡¨πŸ‡¦Canada pub497

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pub497
  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States matthand Riverdale Park, Maryland

    Hi @pub497,

    Thank you for submitting the bug report. I'm not able to reproduce your bug. Can you please check that you ran 'drush cr' before the 'drush fr' commands? We checked the latest release and there's an update hook that should run and flush the container cache. This would fix the error your seeing.

  • πŸ‡¨πŸ‡¦Canada pub497

    Thanks for checking @Matthand, I think the issue is on my build process here. I update the modules with composer, and then put site into maintenance mode with drush state-set system.maintenance_mode 1 this is actually what triggered the ArgumentCountError: Too few arguments to function... error, so it's not actually related to feature revert.

    However I tried clearing caches several ways (drush cr, and drush eval "drupal_flush_all_caches();")
    prior to putting into maintenance but it still throws that error from features when putting into maintenence mode prior to running drush updb command. I haven't checked to see if running updb before putting into maintenance works, but probably don't want to do it that way anyway.

  • Status changed to Closed: works as designed over 1 year ago
  • πŸ‡¨πŸ‡¦Canada pub497

    Hey so this can be closed I think, running updb, then clearing cache , and then setting into maintenance mode again seems to wor

Production build 0.71.5 2024