Update generated code

[async-aws-bot]

The AWS API contract changed with version 1.3.0.

This PR contains the new definition for Services.

[jderusse]

It looks like failures are related to recent changes in Symfony main branch

AsyncAws\Symfony\Bundle\Tests\Functional\BundleInitializationTest::testInitBundle
require(/tmp/NyholmBundleTest/cache66ed173c6f4f79.44587021/ContainerOEapCS4/getServicesResetterService.php): Failed to open stream: No such file or directory

are you aware of such bug @nicolas-grekas / @stof
For reference, it started 2 days ago

[stof]

The error message makes me think it might be related to symfony/symfony#58240 as that's the recent change related to the service resetter service. But this looks weird to me.

[stof]

weird thing is that I don't get those errors locally.

[jderusse]

weird thing is that I don't get those errors locally.

I reproduced with the following steps (extracted form the .github/workflows/ci.yml file)

composer config minimum-stability dev
composer require --dev --no-update "phpunit/phpunit=9.6.*"
composer update --no-interaction --prefer-dist --optimize-autoloader
./vendor/bin/simple-phpunit install
./vendor/bin/simple-phpunit src/Integration/Symfony/Bundle/tests/Functional/ --stop-on-failure

[stof]

yeah, I forgot to use dev stability

[jderusse]

ok, got it.
Because Nyholm\BundleTest\TestKernel cleanup the cache/log on Kernel::shutdown and the new PR calls the container services_resetter after the shutdown

I believe the services_resetter shouldn't be called before kernel shutdown

[stof]

I found the cause of the issue:

KernelTestCase first shutdown the kernel and then resets the container, which now involves getting the service_resetter service.
TestKernel from nyholm/symfony-bundle-test deletes the content of the cache directory during shutdown (by default), which puts the compiled DI container in a corrupted state (any service for which the compiled code is in a separate file cannot be instantiated once those files are gone). Using $kernel->setClearCacheAfterShutdown(false) should avoid that issue.

[jderusse]

Using $kernel->setClearCacheAfterShutdown(false) should avoid that issue.

meh.. I don't want my disk to be fill with obsolete cache, because Symfony tries to use a closed container/kernel.

IMHO this should be fix in Symfony symfony/symfony#58327

[stof]

@jderusse I'm preparing a fix in nyholm/symfony-bundle-test