Skip to content
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

console-en not included with project #508

Closed
girdzijauskas opened this issue Aug 13, 2019 · 10 comments
Closed

console-en not included with project #508

girdzijauskas opened this issue Aug 13, 2019 · 10 comments

Comments

@girdzijauskas
Copy link

girdzijauskas commented Aug 13, 2019

After using
composer create-project drupal-composer/drupal-project:8.x-dev my-project --stability dev --no-interaction

to create a new project, trying to run the console gives you a recursive loop that results in an out of memory on src/vendor/drupal/console-core/src/Utils/TranslatorManager.php on line 108

This is because it's looking for a folder console-en in vendor/drupal, but it's not there.

Upon further inspection, previous projects that I created using the above command include the folder console-en - and the console is fixed by pasting that folder in.

What has changed recently to cause this behaviour?

@zaporylie
Copy link
Contributor

I think it's a change to composer/installers#311 that has been tagged as 1.7.0 yesterday.

@eiriksm
Copy link

eiriksm commented Aug 14, 2019

Currently a fix for this might be:

diff --git a/composer.json b/composer.json
index a5453c7..46e7a27 100644
--- a/composer.json
+++ b/composer.json
@@ -178,6 +178,9 @@
       "drupal/core": [
         "type:drupal-core"
       ],
+      "vendor/drupal/{$name}": [
+        "drupal/console-en"
+      ],
       "drupal/libraries/{$name}": [
         "type:drupal-library",
         "vendor:npm-asset"

@eiriksm
Copy link

eiriksm commented Aug 14, 2019

...and an actual fix in hechoendrupal/drupal-console-core#364

@ghost
Copy link

ghost commented Aug 14, 2019

For me hechoendrupal/drupal-console-core#364 does not fix the issue of the install location. Defining the composer/installers path does.

@eiriksm
Copy link

eiriksm commented Aug 15, 2019

hechoendrupal/drupal-console-core#364 is not supposed to fix the location. It is supposed to support the new location, and also avoid infinite recursion

@joshuaboltzmc
Copy link

I'm having this same issue after upgrading Drupal to 8.7. I assume there was some dependency along the lines with 8.7 that was also upgraded, such as Drupal console updated and now this issue is present. I'm noticing the issue in a Bitbucket pipelines where it's giving this error
Container 'Build' exceeded memory limit.

And inside a local Vagrant for the Drupal site, I am also seeing this error:

../bin/drupal --version
PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/vagrant/docroot/vendor/drupal/console-core/src/Utils/TranslatorManager.php on line 108

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 262144 bytes) in /home/vagrant/docroot/vendor/drupal/console-core/src/Utils/TranslatorManager.php on line 108

@joshuaboltzmc
Copy link

I tried making the change from #508 (comment), but it results in the same error I posted in my earlier comment.

@jcnventura
Copy link
Collaborator

As per hechoendrupal/drupal-console-core#364 (comment), we should add console/language to the .gitignore file.

@jmolivas
Copy link
Contributor

jmolivas commented Sep 9, 2019

This was related to an old PR composer/installers#311 merged to the composer/installers repository that is no longer required.

But got fixed on latest release of the drupal-console project
https://github.com/hechoendrupal/drupal-console/releases/tag/1.9.3

@webflo
Copy link
Member

webflo commented Sep 12, 2019

Thanks! No changes required in this project.

@webflo webflo closed this as completed Sep 12, 2019
mariohernandez pushed a commit to mediacurrent/a11y-training that referenced this issue Oct 25, 2019
mariohernandez pushed a commit to mediacurrent/a11y-training that referenced this issue Oct 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants