Summary (*)

The following commit introduced a static cache for \Magento\Framework\Filesystem\Glob::glob(...)
ef76b7e

Of course this might be the way to go for most processes, but for some cases you should be able to clear this cache. For example

• Sequential functional or unit tests
• Long running processes like consumers

Examples (*)

Pseudo:

1. Call \Magento\Framework\Filesystem\Glob::glob(...)
2. Make some modifications at the file tree
3. Call \Magento\Framework\Filesystem\Glob::glob(...) again, the result is outdated

Proposed solution

Make sure there is always a way to clear the (static) cache.

Severity

• Severity: S0 - Affects critical data or functionality and leaves users with no workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.