composer
Repos
19

Dependency Manager for PHP

26950
4057

Package Repository Website - try https://packagist.com if you need your own -

1591
440

getcomposer.org sources

487
440

Semantic versioning utilities with the addition of version constraints parsing and checking.

2860
64

Tools for working with the SPDX license list and validating licenses.

1369
19

Restart a CLI process without loading the xdebug extension.

2359
27

Events

Created at 1 hour ago
Created at 1 hour ago
issue comment
segmentation fault composer --version under PHP8.1.4

This issue has been automatically marked Stale and will be closed in 15 days if no further activity happens.

Created at 3 hours ago
issue comment
Can't find dll

This issue has been automatically marked Stale and will be closed in 15 days if no further activity happens.

Created at 3 hours ago
started
Created at 4 hours ago
closed issue
Support for Gitlab API v4

Satis v1.0.0 does not support Gitlab API v4. If repository type is set to gitlab and build command is run, Gitlab returns 410 Gone HTTP code (we have 11.0.1 on own server).

Solution: Update composer/composer to at least 1.5, but on my local Satis instance I've updated to 1.7.0 and it's working.

We need this to serve dist packages (Satis takes URLs from Gitlab API) without losing ability to restrict downloading packages only with permissions to repository. archive option in Satis is not a solution because it exposes packages for downloading without checking access rights.

Created at 8 hours ago
create branch
dependabot[bot] create branch dependabot/github_actions/actions/stale-6
Created at 10 hours ago
pull request opened
Bump actions/stale from 5 to 6

Bumps actions/stale from 5 to 6.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Created at 10 hours ago
Created at 11 hours ago
issue comment
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 255

composer update did not work

On Mon, Sep 26, 2022 at 3:14 PM Satyam Khanna @.***> wrote:

if u're working with an existing prooject try running composer update

— Reply to this email directly, view it on GitHub https://github.com/composer/composer/issues/10481#issuecomment-1258024737, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWWNMS7N76URHC5KHPEW65TWAGOVFANCNFSM5MTIOUKQ . You are receiving this because you commented.Message ID: @.***>

Created at 13 hours ago
Created at 14 hours ago
issue comment
Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 255

if u're working with an existing prooject try running composer update

Created at 16 hours ago
Created at 16 hours ago
issue comment
unknown error after host machine update

You seem to be using a custom image with docker compose up. This is beyond what we can offer support for as Sail is intended to just be used with sail up and its unmodified dockerfiles. If you modify them then we cannot help you.

Created at 17 hours ago
pull request opened
Fix typo in "WordPress"

Please check if the PR fulfills these requirements

  • [x] The commit message follows our guidelines
  • [ ] Tests for the changes have been added (for bug fixes/features)
  • [x] Docs have been added/updated (for bug fixes/features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Docs update

What is the current behavior? (You can also link to an open issue here) Typo in word "wordpress"

What is the new behavior (if this is a feature change)? Fixed typo to "WordPress"

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No

Other information: Other occurrences of the word were already spelled correctly.

Created at 17 hours ago
issue comment
unknown error after host machine update

it's the same as running Debian. Besides, I'm not experiencing the problem in wsl-debian, but inside the docker container.

Created at 17 hours ago
Created at 17 hours ago
issue comment
unknown error after host machine update

I cannot provide help with WSL on Windows myself as I don't have a machine sorry.

Created at 17 hours ago
Created at 18 hours ago
Created at 19 hours ago
issue comment
Package "spatie/laravel-ray" is not installed error even when package is not required

Yes, that's understandable @stof. Without having the stack trace it is difficult. Preloading is not enabled in the current setup yet. Opcache is enabled and it was cleared during troubleshooting.

The composer version was 1 when removing the package, wondering if this could have been an issue.

Created at 19 hours ago
issue comment
Package "spatie/laravel-ray" is not installed error even when package is not required

Without knowing where the code was called, there is no way I can even try guessing.

If fixing it required a restart, one guess could be that you enabled PHP's preloading feature and you were still running the preloaded code from before your upgrade.

Created at 19 hours ago
issue comment
Package "spatie/laravel-ray" is not installed error even when package is not required

Thanks for your response @stof

Attempted the same. But no additional logs.

Post this, restarted PHP and NGINX and the error is gone! Wonder what was the issue.

Had cleared the opcache, and other caches.

Any ideas on what could have been wrong here such that it was resolved by PHP and NGINX restart?

Created at 19 hours ago
issue comment
Package "spatie/laravel-ray" is not installed error even when package is not required

I suspect that some code is still trying to get the installed version of that package. Configure your logs to show the stack trace of the exception to see where this call to Composer\InstalledVersions is

Created at 19 hours ago
opened issue
Package "spatie/laravel-ray" is not installed error even when package is not required

My composer.json:

{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The Laravel Framework.",
    "keywords": [
        "framework",
        "laravel"
    ],
    "license": "MIT",
    "require": {
        "php": "^7.4.6",
        "appstract/laravel-opcache": "^4.0",
        "aws/aws-sdk-php-laravel": "^3.6",
        "fideloper/proxy": "^4.2",
        "fruitcake/laravel-cors": "^2.0",
        "guzzlehttp/guzzle": "^6.3",
        "intervention/image": "^2.5",
        "laravel/framework": "^7.24",
        "laravel/sanctum": "^2.6",
        "laravel/socialite": "^4.4",
        "laravel/tinker": "^2.0",
        "socialiteproviders/microsoft": "^3.0",
        "socialiteproviders/yahoo": "^3.0",
        "twilio/sdk": "^6.22"
    },
    "require-dev": {
        "facade/ignition": "^2.0",
        "fzaninotto/faker": "^1.9.1",
        "kitloong/laravel-migrations-generator": "^4.4",
        "krlove/eloquent-model-generator": "^1.3",
        "mockery/mockery": "^1.3.1",
        "mpociot/laravel-test-factory-helper": "^2.1",
        "nunomaduro/collision": "^4.1",
        "nunomaduro/larastan": "^0.7.12",
        "phpunit/phpunit": "^8.5"
    },
    "config": {
        "optimize-autoloader": true,
        "preferred-install": "dist",
        "sort-packages": true
    },
    "extra": {
        "laravel": {
            "dont-discover": []
        }
    },
    "autoload": {
        "psr-4": {
            "App\\": "app/"
        },
        "classmap": [
            "database/seeds",
            "database/factories"
        ]
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\\": "tests/"
        }
    },
    "minimum-stability": "dev",
    "prefer-stable": true,
    "scripts": {
        "post-autoload-dump": [
            "Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover --ansi"
        ],
        "post-root-package-install": [
            "@php -r \"file_exists('.env') || copy('.env.example', '.env');\""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi"
        ]
    }
}

Output of composer diagnose:

Checking composer.json: OK
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
Checking pubkeys:
Tags Public Key Fingerprint: XXXXXXX XXXXXXX 7ECC7CC5 573090D0  87719BA6 8F3BB723 XXXXXXX XXXXXXX
Dev Public Key Fingerprint: XXXXXXX XXXXXXX XXXXXXX XXXXXXX 0C708369 153E328C XXXXXXX XXXXXXX
OK
Checking composer version: You are not running the latest stable version, run `composer self-update` to update (1.10.10 => 2.4.2)
Composer version: 1.10.10
PHP version: 7.4.13
PHP binary path: /usr/bin/php
OpenSSL version: OpenSSL 1.0.2k  26 Jan 2017

For the above setup, the following error is printed in logs:

[2022-09-26 09:51:00][development.ERROR][NULL]: Package "spatie/laravel-ray" is not installed {"exception":"[object] (OutOfBoundsException(code: 0): Package \"spatie/laravel-ray\" is not installed at /var/www/html/userManagement/vendor/composer/composer/src/Composer/InstalledVersions.php:167)"}

spatie/laravel-ray package was being used earlier. However, since it was longer used it was removed from composer.json and composer install was run. With this the package was removed. However, post this, the above error is being printed.

Ran the following commands to clear the caches:

composer dump-autoload

Output:

Generating optimized autoload files
Deprecation Notice: Class League\OAuth1\Client\Tests\TrelloTest located in ./vendor/league/oauth1-client/tests/TrelloServerTest.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\OAuth1\Client\Tests\XingTest located in ./vendor/league/oauth1-client/tests/XingServerTest.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Deprecation Notice: Class League\OAuth1\Client\Tests\ServerStub located in ./vendor/league/oauth1-client/tests/stubs/ServerStub.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi
Discovered Package: appstract/laravel-opcache
Discovered Package: aws/aws-sdk-php-laravel
Discovered Package: facade/ignition
Discovered Package: fideloper/proxy
Discovered Package: fruitcake/laravel-cors
Discovered Package: intervention/image
Discovered Package: kitloong/laravel-migrations-generator
Discovered Package: krlove/eloquent-model-generator
Discovered Package: laravel/sanctum
Discovered Package: laravel/socialite
Discovered Package: laravel/tinker
Discovered Package: mpociot/laravel-test-factory-helper
Discovered Package: nesbot/carbon
Discovered Package: nunomaduro/collision
Discovered Package: socialiteproviders/manager
Package manifest generated successfully.
Generated optimized autoload files containing 8841 classes
composer cc

Output:

Cache directory does not exist (cache-vcs-dir):
Clearing cache (cache-repo-dir): /home/dev/.cache/composer/repo
Clearing cache (cache-files-dir): /home/dev/.cache/composer/files
Clearing cache (cache-dir): /home/dev/.cache/composer
All caches cleared.

Not certain what is going on here. Any help would be much appreciated here.

Created at 19 hours ago
Created at 19 hours ago
Created at 1 day ago
Created at 1 day ago
Created at 1 day ago