[wp-trac] [WordPress Trac] #36455: Invalidate files in opcode cache after plug-in, theme or core update

[WordPress Trac]

#36455: Invalidate files in opcode cache after plug-in, theme or core update
-------------------------------------------+---------------------------
 Reporter:  nigro.simone                   |       Owner:  mikeschroder
     Type:  enhancement                    |      Status:  assigned
 Priority:  normal                         |   Milestone:  5.5
Component:  Upgrade/Install                |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  has-patch needs-testing early  |     Focuses:
-------------------------------------------+---------------------------

Comment (by ayeshrajans):

 Opcache is per-SAPI. This means even if we clear the opcache for CLI, it
 wouldn't affect other SAPIs like fpm or Apache mod_php.

 One of the challenges I faced in Composer Preload plugin is warming up
 cache from a different SAPI. I learned that it's not possible to
 populate/clear opcache of fpm/etc from CLI or the other way around. So I
 propose that we don't even need to bother to clear opcache if the update
 is done by CLI (which might make the tests even more complicated).

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/36455#comment:104>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform