Skip to content

Conversation

@bibumathew
Copy link

  • Added Logic to remove the left over module name after composer package uninstall
  • Updated logic for magento default root directory
  • Removed updateJsonExtra call when magento default root directory is used

@Flyingmana
Copy link
Member

you have mixed a second commit into this pull request.
Pull Requests work better, if you create an own branch for them before.

You can fix this by creating a new branch(for example "patch-1"), change the used branch in your pull request, and then ensure, to only have commits in this branch, you want to have.
Its not good for merging it, when you mix unrelated commits like the root dir change into the Pull Request.

mage2-dev added a commit that referenced this pull request Oct 31, 2014
Added Listener logic to package unintsall
@mage2-dev mage2-dev merged commit e3453d2 into magento:master Oct 31, 2014
okorshenko pushed a commit that referenced this pull request Jan 26, 2016
MAGETWO-44318: [Sample Data] Video Trailers can not be loaded
convenient referenced this pull request in convenient/magento-composer-installer Oct 16, 2020
We had a project fail to composer install with the following error
```
PHP Warning: Uncaught Exception: Warning: require(/var/www/vhosts/example.com/staging/releases/1602858012/setup/config/application.config.php): failed to open stream: No such file or directory in /var/www/vhosts/example.com/staging/releases/1602858012/vendor/magento/framework/Console/Cli.php on line 78 in /var/www/vhosts/example.com/staging/releases/1602858012/vendor/magento/framework/App/ErrorHandler.php:61
Stack trace:
#0 /var/www/vhosts/example.com/staging/releases/1602858012/vendor/magento/framework/Console/Cli.php(78): Magento\Framework\App\ErrorHandler->handler(2, 'require(/var/ww...', '/var/www/vhosts...', 78, Array)
#1 /var/www/vhosts/example.com/staging/releases/1602858012/vendor/magento/framework/Console/Cli.php(78): require()
magento#2 /var/www/vhosts/example.com/staging/releases/1602858012/bin/magento(22): Magento\Framework\Console\Cli->__construct('Magento CLI')
magento#3 {main}
thrown in /var/www/vhosts/example.com/staging/releases/1602858012/vendor/magento/framework/App/ErrorHandler.php on line 61
```

When debugging i could see that a lot of the files from `magento/magento2-base` had not been copied over. I can see an error produced when running with `-vvv`
```
start magento deploy via deployManager
start magento deploy for magento/magento2-base
mkdir(): File exists
start magento deploy for magento/magento2-base
mkdir(): File exists
start magento deploy for magento/magento2-ee-base
jump over deployLibraries as no Magento libraryPath is set
```

I debugged and the issue was that previously on our NFS we had no `pub/media/import` but now we have had one created. 

Now when magento tried to `composer install` it was trying to copy over https://github.com/magento/magento2/blob/2.4-develop/pub/media/import/.htaccess, it faced this `File exists` error and stopped copying over the remainder of the files silently.

I think `composer install` should fail loud and early in these scenarios, removing the error handling entirely allows the exception to bubble up.

Any feedback appreciated
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

Successfully merging this pull request may close these issues.

3 participants