Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Our HEAD is failing due to a metadata leak. It's from order refresh and promotions. I am not sure why this just now appeared.
It might be related to any of the following:
#3134160: Support all operations in query access alters
#3086409: Provide a default query_access handler for core (maybe all?) entity types
#3134363: Support a catch-all QueryAccessEvent for modules that may want to alter all entity queries
Comment | File | Size | Author |
---|---|---|---|
#5 | order_refresh_causes-3161303-5.patch | 4.83 KB | mglaman |
| |||
Screen Shot 2020-07-24 at 10.48.33 AM.png | 145.38 KB | mglaman |
Comments
Comment #2
mglamanPromotions didn’t have query access, and now they do. So they leak metadata during an order refresh. This is due to #3086409: Provide a default query_access handler for core (maybe all?) entity types adding query access to all entities.
Comment #3
mglamanOkay, tracking this down. That issue adds EventOnlyQueryAccessHandler.
It defines no conditions, but dispatches an event for attaching conditions
If we look at \Drupal\entity\QueryAccess\EntityQueryAlter::alter, it always applies cacheable metadata
So it looks like Entity API needs a fix to not bubble cacheability if there are no conditions.
Comment #4
mglamanLinking to an issue in Entity API
Comment #5
mglamanThis wraps the save in a context aware renderer so we can capture and metadata.
Comment #7
mglamanCommitted!