Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
    Arne Jørgensen

    Has the way to declare an extra option for an existing command changed? I want to add an extra option sql-sanitize.

    Adding the option in hook_drush_help_alter() used to work.

    It still lists the option when doing a drush sql-santize —help but executing the command with the option just results in "Unknown option!” (adding —strict=0 works though).

    any one here?
    Matt Andrade
    Hey guys, I having a bit of a problem. I had Drush 7.3.0 installed just fine and then thought to get drush 8. So I removed drush 7 from composer and now when I try re-install using composer I get:
    ~ ಠ_ಠ $ composer global require drush/drush:dev-master
    Changed current directory to /Users/matt.andrade/.composer
    ./composer.json has been updated
    Loading composer repositories with package information
    Updating dependencies (including require-dev)
    Your requirements could not be resolved to an installable set of packages.
      Problem 1
        - Installation request for drush/drush dev-master -> satisfiable by drush/drush[dev-master].
        - drush/drush dev-master requires codegyre/robo ~1.0.0-beta1 -> satisfiable by codegyre/robo[1.0.0-beta1] but these conflict with your requirements or minimum-stability.
    Installation failed, reverting ./composer.json to its original content.
    Jon Pugh
    Hmmmm drush on gitter, huh ?? ;)
    James Wilson
    so, what is the --storm option all about?
    Matt Andrade
    Hey guys, i’m trying to run drush commands on my install of D8. But when I try drush cr I get: exception 'PDOException' with message 'SQLSTATE[HY000] [2002] No such file or directory'
    Anything I need to check for?
    Carl Parrish
    Anyone using https://bitbucket.org/davereid/drush-patchfile? Sounds like a good way to track patches but today is my first time hearing of it.
    Hello. I am curious where I should ask about beginning assembly.
    Frederick Henderson

    I am running Drush 9.0.0-rc1 in project but it seems I am running out of memory. The global php.ini is setting memory_limit to 32M. I have tried changing this limit on the command line with:
    php -d memory_limit=512M ../vendor/bin/drush --php-options=memory_limit=512M status <drush command>
    and with a copy of the php.ini with the memory_limit set to 512M using:
    php -c ~/.drush/php.ini ../vendor/bin/drush -c ~/.drush/php.ini <drush command>.
    If I run the php:cli drush command using the above two line then run phpinfo(); I see that memory_limit is set to 512M.
    Running the status drush command using the line above that sets the php.ini file I see that it is reporting that it is using '~/.drush/php.ini'

    However, here is the kicker when I run the updb drush command using either of the two lines above I get the following error:

    [error] Drush command terminated abnormally due to an unrecoverable error.
    Error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 8192 bytes) in /home/meosch/l2m.ch-test/releases/20171229-022429/docroot/core/lib/Drupal/Core/Extension/InfoParserDynamic.php, line 22
    [error] The external command could not be executed due to an application error.

    Does anyone know what I am doing wrong or how to make this work?

    Frederick Henderson
    @carl-parrish I used it but then switched to use xendk/bandaid for my Drupal 7 projects. They are very similar but the feature set of bandaid won out for me. For Drupal 8 and composer managed projects I use cweagans/composer-patches with an external patches file and Composer to patch projects.
    @andrade1379 This means drush is trying to connect to the database via the socket but it is not allowed. Try changing the host from localhost(socket) to to use a network connection to the MySQL server in your Drupal websites settings.php file.
    Frederick Henderson
    So much for backward compatablity with long time power Drush users memory -n which was short option for "answer no to all questions" in Drush 8. Now in Drush 9 it is used as the short option for --no-interaction. I am glad the last couple of time when I used -n instead of --no in wasn't anything major. So much for a short form for no now as now there is only the long option. Not sure that was thought through very well, either that or using -n as the no option a long time ago.
    Frederick Henderson
    Does anyone know if there are any plans to bring back the drush pm:list feature where you could add a module name after the command to get information about just that command?
    Right now the only alternative I have found is drush pml |grep module_name. Anyone have something better / shorter than that?
    Carl Parrish
    Thanks @frederickjh that will come in handy Iḿ sure.