- Issue created by @mxr576
- ππΊHungary mxr576 Hungary
Related Slack thread: https://drupal.slack.com/archives/C1BMUQ9U6/p1735897088083149
Also attached the textual representation created via Slack dump.
AI summary:
Participants discuss the problems, including:
1. **State Service Issues**: It has become problematic to access the `state` service during container build time due to caching mechanisms and service dependencies.
2. **Race Conditions and Alternatives**: Mention of related issues like race conditions in development, alternative storage options like key-value storage, and container parameters for performance and minimal complexity.
3. **Testing and Failures**: Observations that the update system and session storage break when `state` is used in compiler passes. Failed tests highlight specific issues triggered by `state` usage.
4. **Recommendations and Challenges**: Advice is given to use key-value storage cautiously and ensure cache clearance. However, achieving this in compiler passes presents challenges due to potential outdated information being cached.
5. **Codebase Observations**: A null return from `$this->requestStack->getCurrentRequest()` was identified as a potential unhandled issue in Drupal core, exacerbated by using `state` in compiler passes.
6. **Discussion on Feasibility**: Some participants recommend changing direction entirely due to the complexities and risks involved.
- π¨π¦Canada Charlie ChX Negyesi πCanada
what has the world come to that drupal issues are utilizing ai summaries I thought y'all are better than this