Problem/Motivation
Cancellation of the warmer cron:
Error: Call to a member function accessCheck() on array in Drupal\warmer_entity\Plugin\warmer\EntityWarmer->loadMultiple() (line 96 of /web/modules/contrib/warmer/modules/warmer_entity/src/Plugin/warmer/EntityWarmer.php)
Drupal 9.4.5
PHP: 8.1
Issue fork warmer-3309435
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
lisa.rae commentedComment #4
lisa.rae commentedComment #6
lisa.rae commentedComment #7
lisa.rae commentedComment #8
frank.dev commentedNote - because "Needs review" for 2.x-dev:
The above error also exists (currently) for the this version.
Comment #9
lisa.rae commentedLast revision to MR expands test coverage to execute queued items via cron after creation, to capture regressions that result in failed queue execution.
Comment #10
frank.dev commentedOK, got it. :-)
Comment #11
lisa.rae commentedFrank.dev Since you reported this bug, I've submitted the patch to fix it and added test coverage, but I'm not the maintainer, we'll have to wait for e0ips0 to accept the MR and merge it, and release a new release version.
In the meantime, if you want to apply the patch with composer and test it, then confirm back that the bug has been fixed, that would be great! All patches typically go through a community peer review process before they are merged into the module.
Have a great day!
Comment #12
frank.dev commentedI'm happy to try that.
Can you please offer me a link to the patch?
(Maybe I'm just blind, but I can't find him here.)
Comment #13
juanjolI've tested the MR and it seems to work correctly, can we probably mark it as RTBC?
To get the patch what I have done is to go to drupalcode.org and in the "Code" drop down button, select "Plain diff". I don't know if there is a more efficient way.
Comment #14
juanjolSorry, I changed the status by mistake. I leave it as Needs review again.
Comment #15
lisa.rae commentedSure thing, Frank.dev! Drupal.org changed the patch process after migrating to Gitlab for code repo hosting, the preferred way to to submit changes to core and contrib is to create a fork of the project, work on your code changes and generate a merge request.
To generate a patch from the MR, you can click the link to the MR (see above or here), and add either
.patchor.diffto the end of the URL, this will generate a patch URL that can then be used by Composer to add the patch (you will need to havecomposer/patchesinstalled for the patch to be applied duringcomposer installorcomposer update).Reference: https://stackoverflow.com/questions/38203139/creating-patch-from-merge-r...
Comment #17
e0ipsoComment #18
e0ipsoThanks all. Merging.
Comment #20
lisa.rae commented@e0ipso -- just a comment regarding classy vs claro -- note that the Classy theme is deprecated and will be removed in Drupal 10, which I why I switched the testing theme to Claro.