After updating to rc1 I am getting the following errors when trying to run update.php. It looks like the autoloader is looking for the ConfigFilterServiceProvider in the wrong place.

Unable to run Update.php

CommentFileSizeAuthor
Selection_530.png234.42 KBChrisSnyder
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

chrissnyder created an issue. See original summary.

bircher’s picture

bircher
Location 🇨🇿
CreditAttribution: bircher at Nuvole commented
Status: Active » Postponed (maintainer needs more info)

Hello
Thank you for the screenshot that shows what exactly is going on.

This is due to the fact that this file no longer exists thanks to: #2873623: use service decoration
However, this is not a problem since when you update the module with composer, the autoloader is rebuilt. It looks as if you had a problem with the apc cache though.

Could you verify that this issue persists when clearing the apc cache and rebuilding the autoloader? if it does it is a very serious issue.

ChrisSnyder’s picture

ChrisSnyder
he/him
CreditAttribution: ChrisSnyder at Unleashed Technologies commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Clearing the apc cache resolved my issue. Thank you for your help!

Dane Powell’s picture

Dane Powell CreditAttribution: Dane Powell at Acquia commented

At least in some environments, it's specifically the APC user cache that needs to be cleared. I'm not sure that this can be done from the command line, since APC maintains separate caches for CLI and Apache, which makes actually doing this cache clear in production a pretty big pain.

greg.harvey’s picture

greg.harvey
Primary language English
CreditAttribution: greg.harvey at Code Enigma commented

This tool, cachetool, might help:
https://github.com/gordalina/cachetool

We use it in deployment scripts to make sure the actual *web server* opcode cache is cleared, to avoid %weirdness. :-)