- Issue created by @pfitzer
- 🇮🇳India viren18febS
HI @pfitzer
I am not able to reproduce the issue in both Drupal 9 & 10. can you please add more info, if you have the same issue. added screenshot for reference. - Status changed to Needs review
about 1 year ago 10:43am 23 October 2023 - 🇮🇳India shiv_yadav
hello pfitzer, i have follow given reproduced step but not got any error.
if any other reproduced step. please provide me. Attached screenshot as well.
Thanks. Only additional info i can give ist, comment as an anomynous user with no auto publish. If i find the time i will setup a clean Drupal dev environment from my live installation and take a look if i can reproduce and debug it there.
Drupal: 10.1
PHP: 8.2The problem is in src/Notify.php 372
The query returns an object and this is used in src/Form/SkipForm.php 105-110
$cids should be an array of numbers, but its an object in it which causes the error in Drupal\Core\Entity\EntityStorageBase->buildCacheId()
- Status changed to Active
about 1 year ago 10:28am 25 October 2023 - 🇳🇴Norway gisle Norway
There isnothing to review here. Setting back to "Active" until there is a MR to review.
- Assigned to Shreya_98
- last update
about 1 year ago 18 pass - @shreya_th opened merge request.
- Issue was unassigned.
- Status changed to Needs work
about 1 year ago 12:34pm 25 October 2023 - 🇳🇴Norway gisle Norway
MR !14 replaces:
$cids = $res_comms + $res_copub + $res_counp;
with
$cids = is_object($res_comms) ? iterator_to_array($res_comms) : [];
I.e. it changes the logic of the code from where
$cids
(i.e. comment identifiers) are aggregated from three different sources to just a single one (converted to an array if necessary). There is no explanation accompanying the MR explaining why this change is logic is done, and whether it still produces a valid result. I don't think this MR does anything more than hide the error message, without fixing the underlying bug. - Assigned to gisle
- 🇳🇴Norway gisle Norway
Updated issue summary with steps to reproduce and proposed resolution.
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 3:24pm 25 October 2023 - 🇳🇴Norway gisle Norway
I think I found the root cause.
A fix is now pushed to the last snapshot of 2.0.x-dev.
Please review.
Hi gisle,
i have tested your changes. Now it really works like expected. For me, this is issue is fixed.
- Status changed to Fixed
about 1 year ago 8:09am 27 October 2023 - 🇳🇴Norway gisle Norway
Moving to fixed. There is 14 days to reopen if anyone spots any regressions.
- Status changed to Needs work
about 1 year ago 8:13am 27 October 2023 - Assigned to gisle
- Status changed to Needs review
about 1 year ago 4:27pm 30 October 2023 - 🇳🇴Norway gisle Norway
I've tried to fix the regressions, and have made extensive manual testing. I hope that I now have covered all bases.
There is a new version of 2-0.x-dev in the repo. Please review.
The GitLab CI framework didn't like this version. I am looking into it, but will appreciate manual tests and reviews from users of this module.
- Issue was unassigned.
I have tested the latest 2-0.x and found no more errors. Seems to work fine
- Status changed to Fixed
about 1 year ago 4:49pm 12 November 2023 - 🇳🇴Norway gisle Norway
Moving to fixed. There is 14 days to reopen if anyone spots any regressions.
Automatically closed - issue fixed for 2 weeks with no activity.