- 🇩🇪Germany Fabianx
While we never got #94 in, it also has other problems.
That said I think we can fix the remaining edge cases, by doing this:
diff --git a/includes/module.inc b/includes/module.inc index 494924f..24e5dd7 100644 --- a/includes/module.inc +++ b/includes/module.inc @@ -833,6 +833,11 @@ function module_hook_info() { * @see module_implements() */ function module_implements_write_cache() { + // The list of implementations includes vital modules only before full + // bootstrap, so do not write cache if we are not fully bootstrapped yet. + if (drupal_static("drupal_bootstrap_finished") != TRUE { + return; + }
and then set the drupal_static at the end of the bootstrap full function.
That way - that at phase is set when it's entered, not when it's completed - would no longer bite us here.
- 🇨🇦Canada joseph.olstad
#122 makes sense to me. I have not yet tested this however.
- last update
about 1 year ago 2,161 pass - 🇮🇹Italy marco
The attached patch implements #122, with an addendum from @peximo to make sure that calling a full bootstrap more than once does not break the logic.
- Status changed to RTBC
9 months ago 7:27pm 11 April 2024 - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - last update
9 months ago Patch Failed to Apply - Merge request !8831Issue #496170: module_implements() cache can be polluted by module_invoke_all() being called (in)directly prior to full bootstrap completion → (Open) created by apaderno