Requiring new package runs into a timeout #11190
Labels
Comments
|
Could you try again with |
|
I executed the following: and I had another package that was already present in the composer.json that also created a timeout, the error for the second one looks like this: The output for the first one ( At the time of writing, the exception still hasn't occured, I guess I'll update this comment with the rest, as soon as the command is done. EDIT: here's the rest |
|
@Seldaek I think I figured it out. So clearly, this is not a problem of composer itself but on the host machine. But maybe, just maybe, a quick "enough space available on destination device" could be added sometime in the future. You can close this issue, unless you'd like to pursue the idea of an available diskspace check later on. Best Regards |
|
We do have some warning if you have less than 1MB free https://github.com/composer/composer/blob/main/src/Composer/Console/Application.php#L439-L452 - but you didn't see those, maybe we shuold increase the limit a bit? |
|
I think it depends on the systems, but 1MB does indeed seem a bit low. In my case, a standard project can have a |
|
Bumped the warning to appear if things fail and disk space is <100MB, we'll see how this goes. I don't think it's worth the effort to make this configurable tho |
emahorvat52
pushed a commit
to emahorvat52/composer
that referenced
this issue
Feb 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My
composer.json:{ "minimum-stability": "dev", "prefer-stable": true, "config": { "preferred-install": { "cabag/*": "source", "*": "dist" }, "optimize-autoloader": true, "platform": { "php": "8.0" }, "sort-packages": true, "allow-plugins": { "typo3/class-alias-loader": true, "typo3/cms-composer-installers": true, "cweagans/composer-patches": true, "helhum/dotenv-connector": true } }, "repositories": [ { "type": "composer", "url": "https://repo.packagist.com/cabag/" } ], "name": "cabag/project-ci-relaunch-customer", "description": "TYPO3 CMS Base Distribution", "license": "GPL-2.0-or-later", "require": { "b13/justincase": "^1.1", "cabag/ext-customer": "dev-master", "cweagans/composer-patches": "^1.7", "evoweb/recaptcha": "^11.0", "helhum/dotenv-connector": "^3.0", "helhum/typo3-console": "^7.0", "lochmueller/staticfilecache": "^12.3", "t3monitor/t3monitoring_client": "^9.2", "typo3/cms-about": "*", "typo3/cms-adminpanel": "*", "typo3/cms-belog": "*", "typo3/cms-beuser": "*", "typo3/cms-core": "*", "typo3/cms-filemetadata": "*", "typo3/cms-form": "*", "typo3/cms-frontend": "*", "typo3/cms-lowlevel": "*", "typo3/cms-opendocs": "*", "typo3/cms-recycler": "*", "typo3/cms-redirects": "*", "typo3/cms-rte-ckeditor": "*", "typo3/cms-scheduler": "*", "typo3/cms-seo": "*", "typo3/cms-setup": "*", "typo3/cms-tstemplate": "*", "typo3/cms-viewpage": "*", "typo3/minimal": "^11" }, "require-dev": { "typo3/cms-info": "*", "typo3/cms-reports": "*" }, "conflict": { "typo3/cms": "*" }, "extra": { "composer-exit-on-patch-failure": true, "patches": {}, "typo3/cms": { "web-dir": "web/", "cms-package-dir": "{$vendor-dir}/typo3/cms" }, "helhum/dotenv-connector": { "env-file": "config/env/.env" } }, "scripts": { "security-check": "cd ..; ./local-php-security-checker --path=src/composer.lock", "typo3-cms-scripts": [ "cd ../docker/; docker-compose exec -T php rm -rf ../var/cache/*", "cd ../docker/; docker-compose exec -T php ../vendor/bin/typo3cms install:fixfolderstructure", "cd ../docker/; docker-compose exec -T php ../vendor/bin/typo3cms database:updateschema '*'", "cd ../docker/; docker-compose exec -T php ../vendor/bin/typo3cms cache:flush", "cd ../docker/; docker-compose exec -T php ../vendor/bin/typo3cms cache:warmup" ], "post-update-cmd": [ "@typo3-cms-scripts" ] } }Output of
composer diagnose:When I run this command:
I get the following output:
And I expected this to happen:
Installation of required package.
Important additional information: as discussed with Nils Adermann through the packagist.com Customer chat,
composer --no-cache req cabag/ext-cabag-import dev-typo3-v11worked, opposed to first clearing the cache.I also assume that this might be a problem with mac OS Ventura or git 2.38.1, but no matter the case, running with
--no-cachesolved the problem for me.The text was updated successfully, but these errors were encountered: