- Issue created by @Driskell
- π«π·France andypost
- π«π·France andypost
The related issue already commited but it's not enough so probably the issue is complimentary to π Incorrect warning for system requirements for APCu memory Active
- πΊπΈUnited States dww
Indeed, the other issue started as a critical due to repeated test fails on HEAD. We committed a stop-gap to skip that part of the test. Thereβs now an MR there to fix the status report, too, that needs review. But probably best for scope management and history to move that MR here and close that one as the hot-fix-the-tests issue it started as.
- πΊπΈUnited States dww
Iβll work on moving over the code and cleaning up the other issue, stay tuned.
- @dww opened merge request.
- πΊπΈUnited States dww
Opened MR here, with the code from https://git.drupalcode.org/issue/drupal-3539331/-/tree/3539331-fallback-...
Since both myself and @godotislate worked on that MR, adding credit for them, too.
- πΊπΈUnited States dww
Tagging to be smashed.
Also, crediting @driskell for the clear bug report with correct analysis of the bug and accurate proposed resolution. Had @godotislate and I seen this issue while we were scrambling to fix π Incorrect warning for system requirements for APCu memory Active it would have saved some time, since we had to debug why the status report thought 3GB < 32MB and only with a little debugging output did we discover apc.shm_segments was 0 and then search to find it had been removed upstream. π
Pipeline here is mostly green, except for the dreaded package_manager build test fails. π¬ Queued that one to re-run. But this should be ready for review (and hopefully RTBC) now.
Thanks,
-Derek - π¨πSwitzerland berdir Switzerland
Change looks good to me, monitoring project got hit by this as well but worse (division by zero error). Not related to this issue directly, just similar code.
- πͺπ¨Ecuador andres.torres
Hi all!
Just wondering if this issue will be back-ported to D 10.5+ since Im experiencing the same problem.
Thanks in advance for the hard work!
-
alexpott β
committed 60782706 on 11.x
Issue #3538854 by dww, driskell, andypost, godotislate: APCu requirement...
-
alexpott β
committed 60782706 on 11.x
- πΊπΈUnited States dww
Great, thanks! I'll work on a backport MR right now. Stay tuned.
- @dww opened merge request.
- πΊπΈUnited States dww
Yeah, this didn't apply at all. Had to re-implement it in
system.install
(different indentation, etc, etc).https://git.drupalcode.org/project/drupal/-/merge_requests/12988 for 11.2.x and lower.
https://git.drupalcode.org/issue/drupal-3538854/-/pipelines/572272 is basically looking good. I assume we ignore the PHP 8.5 phpunit deprecation warnings for these backport MRs, right?
Back to NR. Probably worth another set of eyes to look at this before the backport is RTBC.
The Needs Review Queue Bot β tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide β to find step-by-step guides for working with issues.
- π¬π§United Kingdom alexpott πͺπΊπ
Committed da29801 and pushed to 11.2.x. Thanks!
Committed and pushed 265731eb2b7 to 10.6.x and 392338a899e to 10.5.x. Thanks!I did a cherry pick back to 10.x and fixed up the tiny conflict on commit.
-
alexpott β
committed 392338a8 on 10.5.x
Issue #3538854 by dww, driskell, andypost, godotislate: APCu requirement...
-
alexpott β
committed 392338a8 on 10.5.x
-
alexpott β
committed 265731eb on 10.6.x
Issue #3538854 by dww, driskell, andypost, godotislate: APCu requirement...
-
alexpott β
committed 265731eb on 10.6.x
- πΊπΈUnited States dww
Thanks! Doesn't look like you actually pushed the commit to 11.2.x. This issue doesn't show it, nor do I see it in Git.
-
alexpott β
committed b0385095 on 11.2.x
Issue #3538854 by dww, driskell, andypost, godotislate: APCu requirement...
-
alexpott β
committed b0385095 on 11.2.x
Automatically closed - issue fixed for 2 weeks with no activity.