line 29 of libraries/src/LibrariesServiceProvider.php reads: $config_factory = $container->get('config.factory');.

As of Drupal 8.4.0, config.factory requires config.typed, which requires validation.constraint. config.typed used to not require validation.constraint, but now that it does, config.typed cannot be instantiated at Runtime during the bootstrapping/ContainerBuilder process, the reason being that validation.constraint has a parent attribute, and ContainerBuilder::createService() will throw an exception if trying to create a service with a parent attribute.

Please see #2915332: Constructing service "validation.constraint" from a parent definition is not supported at build time and #1928868: Typed config incorrectly implements Typed Data interfaces for more details.

I am not sure at the moment if this is considered a bug with Libraries (it being incompatible with D8.4.0), or if it is actually a big with the recent changes to config.typed in D8.4.0.

If you, the developers of Libraries, have any input on the matter, please outline it here.

WARNING

Anyone with Libraries installed cannot currently update to D8.4.0. I have it installed because I have Juicebox installed, which required Libraries. Anyone who doesn't will not be able to install Libraries on 8.4.0.

CommentFileSizeAuthor
#3 Screen Shot 2017-10-11 at 10.25.59 PM.png48.64 KBepophoto

Comments

xeM8VfDh created an issue. See original summary.

xem8vfdh’s picture

xem8vfdh commented
Title: getting 'config.factory' config from container in LibrariesServiceProvider incompatibly with Drupal 8.4.0 » getting 'config.factory' config from container in LibrariesServiceProvider is incompatible with Drupal 8.4.0
Issue summary: View changes
epophoto’s picture

epophoto commented
Issue summary: View changes
StatusFileSize
new Screen Shot 2017-10-11 at 10.25.59 PM.png48.64 KB

I feel like Im missing something stupid so I apologize in advance. When I download the libraries module I don't have this file "libraries/src/LibrariesServiceProvider.php"

cilefen’s picture

cilefen commented
Issue summary: View changes
cilefen’s picture

cilefen commented
Issue summary: View changes
xem8vfdh’s picture

xem8vfdh commented

hmmm, good point @epophoto, I also do not see it in the 8.x-3.x repo here: http://cgit.drupalcode.org/libraries/tree/src?h=8.x-3.x

But I do see it in my own code base (see LibrariesServiceProvider.png).

I will keep looking into it and let you know. Hopefully one of the Libraries devs will chime in and know where this came from.

-------------------------------

I see it mentioned here, bit it looks like it was deleted in patch 2825940.patch: https://www.drupal.org/node/2825940

Maybe I was running an old version of Libraries module? I don't think so, but I will restore a backup and check.
------------------------------
Ahhhh, I was running an old version of Libraries (8.x-3.x-dev (2016-Nov-13)), the reason being that last time I tried to update, it broke my site. I will try to see if I can update libraries now without breaking anything.
------------------------------
The Libraries API update from 8.x-3.x-dev (2016-Nov-13) is still causing problems for me. Opened #2915809

xem8vfdh’s picture

xem8vfdh commented
Related issues: +#2915809: Updating from 8.x-3.x-dev (2016-Nov-13) to current 8.x-3.x-dev crashes update.php
xem8vfdh’s picture

xem8vfdh commented

Confirmed this was an issue with the specific 8.x-3.x-dev (2016-Nov-13) Libraries version I was running, and that it is not an issue with the newest version of Libraries 8.x-3.x-dev. If you experience this issue, try updating Libraries and re-running the core update.

My Solution

  1. restore backup
  2. update Libraries Module from 8.x-3.x-dev (2016-Nov-13) to latest 8.x-3.x-dev
  3. Get Pantheon support to restart my webstie container to get around Fatal Error cause by step above (more)
  4. run update.php for good measure
  5. update core to 8.4.0
xem8vfdh’s picture

xem8vfdh commented
Status: Active » Closed (works as designed)