Make APCu requirements errors precise and explanatory

Changes caused a CI issue

Fixed failed commands on #19
Attached patch against Drupal 10.1.x

The change/work is being done in the MR switching to a patch just adds noise. So moving to NW to get the work in the MR

Thank you for updating the MR.

Tested this manually and verified the message on the status report page.
For testing I tweaked the numbers to make sure a new message appeared and confirmed that as well.

Looks good to me

This is a definite improvement, thank you!

Adding credit for @colan for the original report, @cilefen, @Chi, and @smustgrave for review and manual testing, @markdorison for work on the MR, @solideogloria for confirming this is still an issue at the reviewer's request, and @pooja saraah for helping fix the PHPCS error (but agreed that next time the change should be added to the MR directly.

As this is a string and render array change, I committed it to 10.1.x only.

xjm → closed merge request !2628

Automatically closed - issue fixed for 2 weeks with no activity.

I am getting this error in Drupal 10.

What happens if the PHP APCu caching memory becomes exhausted - is it just the page loads slowly = not too bad, or somethine like white screen of death = very bad?
.

My main grievance is that this APCu message is categorised as an error. It is certainly not an error, as it does not prevent my Drupal site from functioning normally. At least it should be re-categorized as a warning, not an error.
Plus of course, make the message more explanatory.

The last comment here is the reason I searched for an existing issue. My vote for "warning" instead of "error".

Bot ate my credit for committing this apparently. Fixing that.

To those posting on the closed issue, you are better off filing new issues in the queue. People don't look at closed issues.