guzzle-description-loader dependency is broken (in 9.3 branch)

As this is blocking the option of removing the users (and somehow the patch is not applied fully in the composer.lock when I am doing composer update drupal/http_client_manager -W), could we also have a 9.3.11 release when this is merged, please?

Hi there,
sorry for the long wait. I'm gonna fix it ASAP.

Hi @gorkagr
I just released version 9.3.11 with your fix.

Thanks for your contribution and sorry for the delay.

Regards,
aronne

aronne → closed merge request !15

Than you very much!!

I still get this error with 9.3.11:

Fatal error: Declaration of Guzzle\Service\Loader\FileLoader::load(mixed $resource, ?string $type = null): mixed must be compatible with Symfony\Component\Config\Loader\LoaderInterface::load($resource, $type = null) in /var/www/vendor/fatal-error/guzzle-description-loader/src/FileLoader.php on line 27

hi @achon

After upating to 9.3.11 (therefore this pacth), all is good.
But it seems your symfony is a bit outdated, as

Symfony\Component\Config\Loader\LoaderInterface::load($resource, $type = null)

seems to be a bit old code

Which version of Drupal / PHP are you?

Just to see the version that I got installed of symfony:

$ ddev composer info symfony/config
name     : symfony/config
descrip. : Helps you find, load, combine, autofill and validate configuration values of any kind
keywords : 
versions : * v7.0.7
released : 2024-04-18, 1 month ago
...

I'm on latest Drupal 9.5.x - so unsupported core release.

That means that Symfony components are either version 4.4.x or 5.4.x, if you look at the official composer.json from core.

name     : symfony/config
descrip. : Helps you find, load, combine, autofill and validate configuration values of any kind
keywords : 
versions : * v4.4.44
released : 2022-07-20, 1 year ago

@achton, i opened https://www.drupal.org/project/http_client_manager/issues/3451503 🐛 Revert #3446808 and rename branch 3.x Fixed as a follow-up to revert this change (so u can still use 9.x without pinning the version), but also to propose a renaming of 3.x so it uses a proper versioning :)

Apologies

Automatically closed - issue fixed for 2 weeks with no activity.