Problem/Motivation

MigrateExecutable has a lot of code devote to managing and reclaiming memory, since memory usage is quite relevant to migration. There's nothing wrong with this code per se, but we'd like to remove MigrateExecutable entirely before Drupal 9. To that end, let's move all the memory management code into a new internal class (Drupal\migrate\MemoryManager) and have MigrateExecutable's constructor instantiate it.

The new MemoryManager class will be explicitly internal because it is not an API. Eventually we may want to add an interface to it (and possibly plugin-ize it), at which point we can remove the internal designation, but that's all way out of scope for this issue. For now, we just want to remove as much code from MigrateExecutable as we can.

Cool enough I implemented it and replaced my wonky hook_row_alter :-D

I don't like the setMessage but our message "service" logic is just all over and I wasn't sure how to handle it.

Remaining tasks

Change record - Explain why the threshold is 0.9 and the memory limit is 0.85

i have added the facet module along with views. I am using views ajax, while clicking facet module filter values are send to views Ajax controller. When i remove filter values it has to show all views values.while loading all values(to load all values it takes time) if click another filter that filter values are loaded in ajax quickly(fewer view values loaded in ajax quickly) before previous ajax values. After that only previous ajax values loaded. I want to discuss the possibility of setting ajax request count based on that views values need to render even if first ajax request loaded after second ajax request, second ajax request values need to render in views page(based on ajax request order, ajax response, need to send)

Problem/Motivation

There is no need to use t() in tests, unless we're testing translations, however in core we do not follow this consistently, which does not set a good example for new contributions.

In #3133726: [meta] Remove usage of t() in tests not testing translation we identified there are severals of calls to t() in calls to assertFieldByName(), assertFieldByXpath() and assertNoFieldByXPath() and that removing all these in one go seems to be a suitable way of attacking this problem.

Proposed resolution

Identify and remove all calls to t() wrapped in calls to assertFieldByName(), assertFieldByXpath() and assertNoFieldByXPath(), except those used by translation-related code (if any).

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Problem/Motivation

CommentLazyBuilders always check the default entity language. Even when you view a comment translation you will get links to the default language instead of the translation you are viewing.

Steps to reproduce:

1. Make your comment type translatable
2. Create a comment and then translate it
3. View the comment translation, e.g. visit /fr/comment/1
4. Inspect the local tasks links, you will see that they point to the default language, like /comment/1/edit instead of the translation /fr/comment/1/edit

In the available variables section of core/modules/book/templates/book-tree.html.twig within items we have (amongst others):

* - url: The book link URL, instance of \Drupal\Core\Url.

However this is no longer true. In https://www.drupal.org/project/drupal/issues/3010378 it was changed from a Url object to a string in the format entity:node/12345. We found this after updating Drupal Core and finding some of our custom code was no longer working.

Proposed resolution:
* Either revert the change, so that url continues to be a Url object
or
* Update the book-tree.html.twig documentation and publish a change record so anyone relying on the current/previous behaviour is able to update their code accordingly

Problem/Motivation

There are many misspelled words in the drupal core [9.1.x-dev].
Currently the Drupal dictionary contains words that are misspelt in core at the time we added spellchecking to core. It might be necessary to regenerate the dictionary if misspelt words have been fixed without removing them from the Drupal dictionary.

Proposed resolution

Refer to https://www.drupal.org/node/3122084 follow the steps to regenerate the dictionary and fix the misspelled words.
Make child issues for the same for modules.

Remaining tasks

1. Fixing the misspelled words.
2. Regenarating the dictionary.

User interface changes

API changes

Data model changes

Release notes snippet

Problem/Motivation

On PHP 8 we need to ensure that the fragment is not set to an empty string. See the behaviour change https://3v4l.org/HsvX0

https://github.com/php/php-src/blob/master/UPGRADING#L430

Without this fix

      // Ensure an empty fragment of # in the URI is discarded as expected.
      [
        'entity:test_entity/1#',
        [],
        'entity.test_entity.canonical',
        ['test_entity' => '1'],
        NULL,
        NULL,
      ],

from \Drupal\Tests\Core\UrlTest::providerTestEntityUris() will fail.

Proposed resolution

To maintain PHP 7 behaviour we need to check the value before setting it.

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

Release notes snippet

None

Part of #3116859: [meta] Fix Drupal.Array.Array.LongLineDeclaration coding standard.

Problem/Motivation

Follow up #2729597: [meta] Replace \Drupal with injected services where appropriate in core

Proposed resolution

Replace all of them with IoC injection where possible

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Problem/Motivation

Cache of entities are not invalidated when the entity label changes.

Steps to reproduce for nodes & breadcrumbs (from #3):

1. Create a node with title 'Title A'.
2. Change the title to 'Title B' and check the 'Create new revision'.
3. Open the Revisions tab > Breadcrumb shows the right title (Title B).
4. Change the title to 'Title C' and check the 'Create new revision'.
5. Open the Revisions tab.

Expected: The title in the breadcrumb is 'Title C'.
Actual: the title in the breadcrumb is 'Title B'.

Steps to reproduce for users (from #48):

1. 1. Log in
2. 2. Edit your username and save.
3. 3. Return to the edit screen for your user account.

Expected: Breadcrumb shows your new username
Actual: You'll see your old username is still utilised in the breadcrumb.

Proposed resolution

Allow attaching cacheability metadata to titles with a new CacheableTitleResolverInterface that returns a static or dynamic title (with cacheable metadata).

Problem/Motivation

There's a @todo in the docblock of seven_preprocess_fieldset__media_library_widget that says:

@todo Remove this when https://www.drupal.org/project/drupal/issues/2999549 lands.

There's also todo in Drupal\media_library\Plugin\Field\FieldWidget\MediaLibraryWidget that says:

@todo Use a link here, and delete seven_preprocess_fieldset__media_library_widget(), when https://www.drupal.org/project/drupal/issues/2999549 lands.

Proposed resolution

Address the todo comments.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Problem/Motivation

The order of the media items is messed up when using Media Library widget in a particular use-case (when arranging the media items and after that inserting a new media).

Steps to reproduce:
1. Create a Content Type with an unlimited media reference field.
2. In form display for that field chose the Media library widget.
3. Add new content of that Content Type.
4. In the media field add more than 3 media items.
5. Save the node.
6. Go to the edit page of that node.
7. Re-arrange the media by drag and drop.
8. Press the "Add Media" button.
9. Select a new image to insert and press the "Insert Selected" button.
10. The media items will be ordered correctly but their weights will be messed up. You can look at them by pressing "Show media item weights".
11. Save node.

Expected behavior:
The order of the media should remain the way it was arranged before inserting a new image and the new image should be the last one.

Current behavior:
The media items order is not the way it was arranged.

Proposed resolution

I didn't find what was the cause of this problem but one of the solutions/workarounds will be to get the weights from the $field_state (which are the correct ones) and put them in the $element in the updateWidget memthod.

Remaining tasks

Add tests.

Problem/Motivation

PHPUnit 8 fails somewhat aggressively for its own deprecations, with TestCase::addWarning(). New methods that don't exist for PHPUnit 6 are required for tests to pass on PHPUnit 8. To work around this, Drupal 9.0 overrode TestCase::addWarning() to skip warnings for all new deprecation in PHPUnit 8, in \Drupal\Tests\Traits\PHPUnit8Warnings. This works differently than the suppression of deprecation failures from the Symfony PHPUnit bridge.

As we cleaned up core's use of the deprecated methods, we removed each warning from the list of silenced warnings. This has mostly happened during Drupal 9.0's beta, while 8.7 is still supported and 9.1.x is open for new development..

Because the warnings are being raised by PHPUnit itself and not the PHPUnit bridge, this means marking tests @legacy or using --suppress-deprecationson Drupal CI is not sufficient to avoid a test failure. It also means that tests that need to assert things related to these assertions can't be compatible with 8.7 and 9.0's beta at the same time, because even though we backported foward-compatibility shims all the way into 8.8 during its stable release, we can't and won't backport new APIs to the security-support-only branch. (Furthermore, a couple methods could not be backported to Drupal 8 because they would not be straightforward to implement on PHP 7.0.)

Proposed resolution

Normally, we don't add disruptive changes like new deprecations to a branch after it's in beta. Disruptive changes should only be going into 9.1.x at the moment. Unsilencing a deprecation is a disruptive change.

So, restore the full list of PHPUnit8 warnings to ignore in 9.0.x only. That way, 9.0 compatibility doesn't require dealing with the full gamut of "new" deprecations from PHPUnit 8, and more module can use 8^ || 9^ compatibility rather than ^8.8. || ^9. 9.1.x will still fail if we accidentally reintroduce usage of one of the deprecated methods, and since the backport policy requires things be committed to 9.1.x first, that means we're unlikely to regress 9.0 either. (Both 9.0 and 8.9 will need to be compatible with PHP 8, and therefore PHPUnit 9.)

Remaining tasks

Decide if this is actually the best way to go, or if we do want these fails to force contrib to be forward-compatible with PHPUnit 9 (and therefore PHP 8).

User interface changes

API changes

Data model changes

Release notes snippet

Hello,

I've been studied the media core module, and I have found that it is not possible to support multiple websites with the same provider at the same time. I think it is really annoying that it supports only the centralized approach because the internet is supposed to be decentralized.

The name of the provider is fixed by the service that you use. I will take the example of my usecase to be easier to understand. So my usecase is the PeerTube, a decentralized video platform.

So oEmbed imposes us the provider name as we can see in those examples:

For Youtube:
https://www.youtube.com/oembed?url=https://www.youtube.com/watch?v=xHLes...
provider_name = Youtube

For PeerTube:
https://framatube.org/services/oembed?url=https%3A%2F%2Fframatube.org%2F...
provider_name = PeerTube
https://peertube.cpy.re/services/oembed?url=https%3A%2F%2Fpeertube.cpy.r...
provider_name = PeerTube

Consequently we have something like that in the ressource fetcher yml file pointed by the oembed_providers_url variable from media.settings

[
  0	=> {
    provider_name:	"PeerTube",
    provider_url:	"https://framatube.org",
    endpoint: [
      0 => {	
        url	"https://framatube.org/services/oembed",
        discovery	true
      }
    ]
  },
  1	=> {
    provider_name:	"PeerTube",
    provider_url:	"https://peertube.cpy.re",
    endpoint: [
      0 => {	
        url	"https://peertube.cpy.re/services/oembed",
        discovery	true
      }
    ]
  }
]

After that we arrive to the part that the media core module fails totally.

In Drupal\media\OEmbed\ProviderRepository

$keyed_providers = [];
    foreach ($providers as $provider) {
      try {
        $name = (string) $provider['provider_name'];
        $keyed_providers[$name] = new Provider($provider['provider_name'], $provider['provider_url'], $provider['endpoints']);
      }
      catch (ProviderException $e) {
        // Just skip all the invalid providers.
        // @todo Log the exception message to help with debugging.
      }
    }

If we read that code, it will iterate on every provider and fill the $keyed_providers variable. But of course, it will erase the data from the other websites with the same provider. After that, the core media module will be ok but only for the last website you have declared with the common provider.

I will try to work on that but this will probably be a big change on how the media module uses oEmbed.

For those who want to work on that, the core doesn't allow to override the oembed_providers_url setting yet. So set it manually or there is already an issue on drupal.org: #2999018 Expose oEmbed provider URL setting in the Media configuration form

I have a working module that supports only one website of Peertube because of this issue. If you want to debug this issue, it will give you a usecase to debug: PeerTube

Thank you to those who will help me to resolve this issue.

Problem/Motivation

In the patch that marks the Workspaces module as stable, we found that the workspace entity type is missing some REST and JSON:API test coverage.

Proposed resolution

Add the missing test coverage.

Remaining tasks

Review.

User interface changes

Nope.

API changes

Nope.

Data model changes

Nope.

Release notes snippet

TBD.

When you migrate nodes of a certain content type from, say D7, into D8.9 (using the migrate_upgrade module) and on the D8 site the Content Moderation module is enabled with a Workflow defined for that content type, then ALL entities (nodes) of the content type will be saved with their "status" (Published flag) OFF and their workflow state set to Draft, regardless of whether those nodes were Published or Unpublished on the D7 site.

The desired behaviour is that migrated/imported content has its Publshied/Unpublished flag set identical to the source (D7)
and that the generate workflow state in D8 is consistent with that state, i.e a workflow state of Published when the status flag is Published and Draft when Unpublished.

Patch to follow.

Working on #3138078: Add a 'void' return typehint to custom assert* methods, it looks like BigPipeTest::assertSetsEqual is just returning a value, but that is not an assertion by itself, nor the returned value is used for anything.

However, converting to

   /**
    * Asserts whether arrays A and B are equal, when treated as sets.
    */
-  protected function assertSetsEqual(array $a, array $b) {
-    return count($a) == count($b) && !array_diff_assoc($a, $b);
+  protected function assertSetsEqual(array $a, array $b): void {
+    $this->assertTrue(count($a) == count($b) && !array_diff_assoc($a, $b));
   }
 
   /**

leads to failure of the assertion, so I wonder if there's an underlying bug.

Problem/Motivation
Progress throbber position and styling are incorrect while viewing in table display as compared with other displays.

Steps to replicate
Example:
1. Go to admin/structure/block and click on place block to check the throbber effect.
2. After that click on the place block button from place block modal popup form and check the throbber effect.

See the below screenshots

I'm trying to upgrade to Drupal 8.9.1 from 8.7.14, and after some pain, I finally got things working, but then my build failed in my CircleCI process. I tracked it down to what seems to be drupal/core-dev. It seems that having composer/composer as a local package messes things up when you do composer install --no-dev, which I didn't try until my build ran in CircleCI. I was able to reproduce the issue locally though when running composer install --no-dev in my local dev environment. I was following this info for this part of the upgrade/migration: https://www.drupal.org/docs/updating-drupal/migrate-composer-project-for...

I haven't done this yet, but I'm going to simply try removing drupal/core-dev from my project. The site that I'm in charge of doing dev for was originally set up by a 3rd-party vendor, and they had the webflo/drupal-core-require-dev package in there. So, I figured I might need to keep the new one, but I haven't tested it yet.

I guess, another potential workaround could be to specify the exact instance of Composer (global vs. local), but I would imagine that's only possible if it's always installed in the same place across envs where it's used, so not ideal.

Steps to Reproduce

1. Put drupal/core-dev as a required dependency for development along with the rest of a normal Drupal 8.9.1 project.
2. Run composer install to do a normal install (which you might do as part of your CI process to run tests first)
3. Run composer install --no-dev

Expected Behavior

Simply run composer install --no-dev as normal without errors.

What Actually Happened

Error happened, which seems to be from composer/composer getting removed as a dev dependency. I'm not super familiar with the inner workings of Composer, but from what I can tell from that error, the composer/composer package is the Composer instance being used when running composer install --no-dev but in the middle of that process we remove composer/composer package.

I could also confirm that when I do run the normal install (composer install), my version of Composer is 1.10.8, which matches what gets installed by drupal/core-dev package. Also, which composer points to the "local" package version.

If I run composer install --no-dev, after it fails, the version and which of Composer point to my globally installed version.

I'm using Lando for local dev. This occurred in my CircleCI build as well, so I have no reason to suspect this has anything to do with Lando.

"composer install --no-dev -vvv" with Error:

lando 00:23:59 VERBOSE ==> starting bootstrap at level engine... 
lando 00:23:59 VERBOSE ==> config bootstrap beginning... 
lando 00:23:59 DEBUG ==> emitting event pre-bootstrap-config 
lando 00:23:59 DEBUG ==> plugin lando-core loaded from /snapshot/lando/build/cli/plugins/lando-core/index.js 
lando 00:23:59 DEBUG ==> plugin lando-events loaded from /snapshot/lando/build/cli/plugins/lando-events/index.js 
lando 00:23:59 DEBUG ==> plugin lando-networking loaded from /snapshot/lando/build/cli/plugins/lando-networking/index.js 
lando 00:23:59 DEBUG ==> plugin lando-pantheon loaded from /snapshot/lando/build/cli/plugins/lando-pantheon/index.js 
lando 00:23:59 DEBUG ==> plugin lando-proxy loaded from /snapshot/lando/build/cli/plugins/lando-proxy/index.js 
lando 00:23:59 DEBUG ==> plugin lando-recipes loaded from /snapshot/lando/build/cli/plugins/lando-recipes/index.js 
lando 00:23:59 DEBUG ==> plugin lando-services loaded from /snapshot/lando/build/cli/plugins/lando-services/index.js 
lando 00:23:59 DEBUG ==> plugin lando-sharing loaded from /snapshot/lando/build/cli/plugins/lando-sharing/index.js 
lando 00:23:59 DEBUG ==> plugin lando-test loaded from /snapshot/lando/build/cli/plugins/lando-test/index.js 
lando 00:23:59 DEBUG ==> plugin lando-tooling loaded from /snapshot/lando/build/cli/plugins/lando-tooling/index.js 
lando 00:23:59 DEBUG ==> emitting event post-bootstrap-config 
lando 00:23:59 VERBOSE ==> building proxy config... 
lando 00:23:59 VERBOSE ==> config bootstrap completed. 
lando 00:23:59 VERBOSE ==> tasks bootstrap beginning... 
lando 00:23:59 DEBUG ==> emitting event pre-bootstrap-tasks 
lando 00:23:59 DEBUG ==> autoloaded task config 
lando 00:23:59 DEBUG ==> autoloaded task destroy 
lando 00:23:59 DEBUG ==> autoloaded task info 
lando 00:23:59 DEBUG ==> autoloaded task list 
lando 00:23:59 DEBUG ==> autoloaded task logs 
lando 00:23:59 DEBUG ==> autoloaded task poweroff 
lando 00:23:59 DEBUG ==> autoloaded task rebuild 
lando 00:23:59 DEBUG ==> autoloaded task restart 
lando 00:23:59 DEBUG ==> autoloaded task share 
lando 00:23:59 DEBUG ==> autoloaded task start 
lando 00:23:59 DEBUG ==> autoloaded task stop 
lando 00:23:59 DEBUG ==> autoloaded task version 
lando 00:23:59 DEBUG ==> autoloaded task init 
lando 00:23:59 DEBUG ==> autoloaded task ssh 
lando 00:23:59 DEBUG ==> emitting event post-bootstrap-tasks 
lando 00:23:59 VERBOSE ==> tasks bootstrap completed. 
lando 00:23:59 VERBOSE ==> engine bootstrap beginning... 
lando 00:23:59 DEBUG ==> emitting event pre-bootstrap-engine 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-core/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-pantheon/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-proxy/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-recipes/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-services/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> automoved scripts from /snapshot/lando/build/cli/plugins/lando-sharing/scripts to /home/tom/.lando/scripts and set to mode 755 
lando 00:23:59 DEBUG ==> emitting event post-bootstrap-engine 
lando 00:23:59 VERBOSE ==> engine bootstrap completed. 
lando 00:23:59 VERBOSE ==> bootstrap completed. 
lando 00:23:59 DEBUG ==> emitting event post-bootstrap 
lando 00:23:59 VERBOSE ==> docker-engine exists: true 
lando 00:23:59 VERBOSE ==> docker-compose exists: true 
lando 00:23:59 DEBUG ==> emitting event cli-answers 
lando 00:23:59 DEBUG ==> emitting event cli-composer-answers 
lando 00:23:59 DEBUG ==> emitting event cli-run 
lando 00:23:59 DEBUG ==> emitting event cli-composer-run 
lando 00:23:59 DEBUG ==> emitting event pre-composer 
lando 00:23:59 DEBUG ==> process pid4 running /usr/bin/docker exec centrifyd8_appserver_1 composer cstdio=[inherit, pipe, pipe], silent=false, mode=attach, detached=false
lando 00:24:00 DEBUG ==> engine is up. 
                                       lando 00:24:00 DEBUG ==> docker is running. 
                                                                                   Reading ./composer.json
Loading config file /var/www/.composer/auth.json
Loading config file ./composer.json
Checked CA file /etc/ssl/certs/ca-certificates.crt: valid
Executing command (/app): git branch --no-color --no-abbrev -v
Reading /var/www/.composer/composer.json
Loading config file /var/www/.composer/auth.json
Loading config file /var/www/.composer/composer.json
Loading config file /var/www/.composer/auth.json
Reading /var/www/.composer/auth.json
Reading /app/vendor/composer/installed.json
Reading /var/www/.composer/vendor/composer/installed.json
Loading plugin zaporylie\ComposerDrupalOptimizations\Plugin
Required tags were not explicitly set so the zaporylie/composer-drupal-optimizations set default based on project's composer.json content.
extra.commerce-drupal-optimizations.require.symfony/symfony: '>3.4'
lando 00:24:00 VERBOSE ==> checking docker version compatibility... 
                                                                    lando 00:24:00 DEBUG ==> compatibility results name=compose, link=https://docs.docker.com/compose/install/#install-compose-on-linux-systems, wants=1.23.0 - 1.25.5, version=1.25.5, semversion=1.25.5, semmin=1.23.0, semmax=1.25.5, dockerVersion=true, satisfied=true, name=engine, link=https://docs.docker.com/engine/install/, wants=18.09.3 - 19.04.0, version=19.03.6, semversion=19.3.6, semmin=18.9.3, semmax=19.4.0, dockerVersion=true, satisfied=true
                                                                 Loading plugin rvtraveller\QuicksilverComposerInstaller\QuicksilverComposerInstallerPlugin
Loading plugin Drupal\Composer\Plugin\Scaffold\Plugin
Loading plugin Drupal\Console\Composer\Plugin\Extender
Loading plugin cweagans\Composer\Patches
Loading plugin Composer\Installers\Plugin
Loading plugin Hirak\Prestissimo\Plugin
Running 1.10.8 (2020-06-24 21:23:30) with PHP 7.4.7 on Linux / 5.3.0-7648-generic
Reading ./composer.lock
Gathering patches for root package.
Removing package drupal/entity_browser so that it can be re-installed and re-patched.
  - Removing drupal/entity_browser (2.5.0)
Deleting web/modules/contrib/entity_browser - deleted
Loading composer repositories with package information
Installing dependencies from lock file
Reading ./composer.lock
Resolving dependencies through SAT
Looking at all rules.

Dependency resolution completed in 0.006 seconds
Analyzed 704 packages to resolve dependencies
Analyzed 2424 rules to resolve dependencies
Package operations: 1 install, 0 updates, 50 removals
Installs: drupal/entity_browser:2.5.0
Removals: theseer/tokenizer, symfony/phpunit-bridge, symfony/lock, symfony/browser-kit, squizlabs/php_codesniffer, seld/phar-utils, seld/jsonlint, sebastian/version, sebastian/resource-operations, sebastian/recursion-context, sebastian/object-reflector, sebastian/object-enumerator, sebastian/global-state, sebastian/exporter, sebastian/environment, sebastian/diff, sebastian/comparator, sebastian/code-unit-reverse-lookup, phpunit/phpunit-mock-objects, phpunit/phpunit, phpunit/php-token-stream, phpunit/php-timer, phpunit/php-text-template, phpunit/php-file-iterator, phpunit/php-code-coverage, phpspec/prophecy, phar-io/version, phar-io/manifest, overtrue/phplint, n98/junit-xml, myclabs/deep-copy, mikey179/vfsstream, justinrainbow/json-schema, jcalderonzumba/mink-phantomjs-driver, jcalderonzumba/gastonjs, fabpot/goutte, drupal/drupal-extension, drupal/core-dev, drupal/coder, doctrine/instantiator, composer/xdebug-handler, composer/spdx-licenses, composer/composer, composer/ca-bundle, behat/transliterator, behat/mink-goutte-driver, behat/mink-extension, behat/mink-browserkit-driver, behat/gherkin, behat/behat
  - Removing theseer/tokenizer (1.1.3)
  - Removing symfony/phpunit-bridge (v3.4.42)
  - Removing symfony/lock (v3.4.42)
  - Removing symfony/browser-kit (v3.4.42)
  - Removing squizlabs/php_codesniffer (3.5.5)
  - Removing seld/phar-utils (1.1.0)
  - Removing seld/jsonlint (1.8.0)
  - Removing sebastian/version (2.0.1)
  - Removing sebastian/resource-operations (1.0.0)
  - Removing sebastian/recursion-context (3.0.0)
  - Removing sebastian/object-reflector (1.1.1)
  - Removing sebastian/object-enumerator (3.0.3)
  - Removing sebastian/global-state (2.0.0)
  - Removing sebastian/exporter (3.1.2)
  - Removing sebastian/environment (3.1.0)
  - Removing sebastian/diff (2.0.1)
  - Removing sebastian/comparator (2.1.3)
  - Removing sebastian/code-unit-reverse-lookup (1.0.1)
  - Removing phpunit/phpunit-mock-objects (5.0.10)
  - Removing phpunit/phpunit (6.5.14)
  - Removing phpunit/php-token-stream (2.0.2)
  - Removing phpunit/php-timer (1.0.9)
  - Removing phpunit/php-text-template (1.2.1)
  - Removing phpunit/php-file-iterator (1.4.5)
  - Removing phpunit/php-code-coverage (5.3.2)
  - Removing phpspec/prophecy (v1.10.3)
  - Removing phar-io/version (1.0.1)
  - Removing phar-io/manifest (1.0.1)
  - Removing overtrue/phplint (2.0.2)
  - Removing n98/junit-xml (1.0.0)
  - Removing myclabs/deep-copy (1.10.1)
  - Removing mikey179/vfsstream (v1.6.8)
  - Removing justinrainbow/json-schema (5.2.10)
  - Removing jcalderonzumba/mink-phantomjs-driver (v0.3.3)
  - Removing jcalderonzumba/gastonjs (v1.2.0)
  - Removing fabpot/goutte (v3.2.3)
  - Removing drupal/drupal-extension (v3.4.1)
  - Removing drupal/core-dev (8.9.1)
  - Removing drupal/coder (8.3.9)
Executing command (/app/vendor/drupal/coder): git show-ref --head -d
Executing command (/app/vendor/drupal/coder): git status --porcelain --untracked-files=no
Executing command (CWD): rm -rf '/app/vendor/drupal/coder'
  - Removing doctrine/instantiator (1.3.1)
  - Removing composer/xdebug-handler (1.4.2)
  - Removing composer/spdx-licenses (1.5.3)
  - Removing composer/composer (1.10.8)
  - Removing composer/ca-bundle (1.2.7)
  - Removing behat/transliterator (v1.3.0)
  - Removing behat/mink-goutte-driver (v1.2.1)
  - Removing behat/mink-extension (2.3.1)
  - Removing behat/mink-browserkit-driver (v1.3.4)
  - Removing behat/gherkin (v4.6.2)
  - Removing behat/behat (v3.7.0)
Gathering patches for root package.
Gathering patches for dependencies. This might take a minute.
Found 16 patches for drupal/core.
Found 1 patches for drupal/adminimal_admin_toolbar.
Found 1 patches for drupal/block_class.
Found 1 patches for drupal/contact_storage.
Found 1 patches for drupal/ctools.
Found 1 patches for drupal/entity_block.
Found 3 patches for drupal/entity_browser.
Found 1 patches for drupal/entity_embed.
Found 1 patches for drupal/facets.
Found 3 patches for drupal/material_admin.
Found 5 patches for drupal/panels.
Found 1 patches for drupal/responsive_preview.
Found 1 patches for drupal/textfield_counter.
Found 1 patches for drupal/video_embed_field.
Found 1 patches for drupal/zurb_foundation.
Found 1 patches for lite.
Found 1 patches for drupal/panelizer.
Found 1 patches for drupal/libraries.
Found 1 patches for drupal/autosave_form.
  - Installing drupal/entity_browser (2.5.0): 
Failed: [ErrorException] 0: include(/app/vendor/composer/../composer/composer/src/Composer/Util/Url.php): failed to open stream: No such file or directory

In ClassLoader.php line 444:
                                                                                                                                  
  [ErrorException]                                                                                                                
  include(/app/vendor/composer/../composer/composer/src/Composer/Util/Url.php): failed to open stream: No such file or directory  
                                                                                                                                  

Exception trace:
  at /app/vendor/composer/ClassLoader.php:444
 Composer\Util\ErrorHandler::handle() at /app/vendor/composer/ClassLoader.php:444
 include() at /app/vendor/composer/ClassLoader.php:444
 Composer\Autoload\includeFile() at /app/vendor/composer/ClassLoader.php:322
 Composer\Autoload\ClassLoader->loadClass() at n/a:n/a
 spl_autoload_call() at /app/vendor/composer/composer/src/Composer/Downloader/FileDownloader.php:270
 Composer\Downloader\FileDownloader->processUrl() at /app/vendor/composer/composer/src/Composer/Downloader/FileDownloader.php:127
 Composer\Downloader\FileDownloader->doDownload() at /app/vendor/composer/composer/src/Composer/Downloader/FileDownloader.php:97
 Composer\Downloader\FileDownloader->download() at /app/vendor/composer/composer/src/Composer/Downloader/ArchiveDownloader.php:38
 Composer\Downloader\ArchiveDownloader->download() at /app/vendor/composer/composer/src/Composer/Downloader/ZipDownloader.php:77
 Composer\Downloader\ZipDownloader->download() at /app/vendor/composer/composer/src/Composer/Downloader/DownloadManager.php:216
 Composer\Downloader\DownloadManager->download() at /app/vendor/composer/composer/src/Composer/Installer/LibraryInstaller.php:197
 Composer\Installer\LibraryInstaller->installCode() at /app/vendor/composer/composer/src/Composer/Installer/LibraryInstaller.php:101
 Composer\Installer\LibraryInstaller->install() at /app/vendor/composer/composer/src/Composer/Installer/InstallationManager.php:173
 Composer\Installer\InstallationManager->install() at /app/vendor/composer/composer/src/Composer/Installer/InstallationManager.php:160
 Composer\Installer\InstallationManager->execute() at /app/vendor/composer/composer/src/Composer/Installer.php:611
 Composer\Installer->doInstall() at /app/vendor/composer/composer/src/Composer/Installer.php:232
 Composer\Installer->run() at /app/vendor/composer/composer/src/Composer/Command/InstallCommand.php:122
 Composer\Command\InstallCommand->execute() at /app/vendor/symfony/console/Command/Command.php:255
 Symfony\Component\Console\Command\Command->run() at /app/vendor/symfony/console/Application.php:987
 Symfony\Component\Console\Application->doRunCommand() at /app/vendor/symfony/console/Application.php:255
 Symfony\Component\Console\Application->doRun() at /app/vendor/composer/composer/src/Composer/Console/Application.php:281
 Composer\Console\Application->doRun() at /app/vendor/symfony/console/Application.php:148
 Symfony\Component\Console\Application->run() at /app/vendor/composer/composer/src/Composer/Console/Application.php:113
 Composer\Console\Application->run() at /app/vendor/composer/composer/bin/composer:62

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...

lando 00:24:01 DEBUG ==> process pid4 finished with exit code 1