Closed (fixed)
Project:
Scheduler
Version:
2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Apr 2024 at 23:44 UTC
Updated:
27 Aug 2024 at 12:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
gcbComment #3
gcbComment #6
jrockowitz commentedWe should use the Symfony\Component\EventDispatcher\EventDispatcherInterface to maintain backward compatibility.
Comment #7
phenaproximaI'm running into this on my project. Patch looks okay to me, and CI is passing, so I guess this is RTBC.
Comment #8
phenaproximaRe-titling for clarity.
Comment #9
jonathan1055 commentedHi gcb, jrockowitz and phenaproxima,
Thanks for working on this. But I am surprised at the issue summary "on a new site with Drupal 10.2.4 ..." is that really correct? Maybe you mean 10.3 or 11.x? Anyway, there is clearly something to fix here, so please can you open a Merge Request so that we can see the gitlab pipeline. Patch testing on drupal.org is being phased out, and all the development here should now be on MRs.
Thanks
Comment #10
phenaproximaHi @jonathan1055 - there is a merge request open and CI is passing. You can see this at the top of this issue. But, for reference...
The merge request: https://git.drupalcode.org/project/scheduler/-/merge_requests/128
The passing tests: https://git.drupalcode.org/issue/scheduler-3437739/-/pipelines/139271
I'm hiding the patches, though, for clarity.
Comment #11
phenaproximaComment #12
jonathan1055 commentedThanks. Sorry I don't know why I missed it. I have rebase the MR and running the pipeline again.
Comment #13
jonathan1055 commentedIn your previous test run, the phpunit tests are only run automatically at the current core version, 10.2 and they pass of course. But the "next minor" phpunit, for core 10.3, have to be triggered manually.
Comment #14
jonathan1055 commentedThe tests at 10.3 still have deprecations, but the actual tests run.
I need to verify if this change is OK at "previous minor" core 10.1 and "previous major" Core 9.5.11 before I commit.
I ran in to a problem with doing that, which I reported on #3441816: All variants run the same Drupal version when the pipeline is triggered via web. It seems that running a pipeline manually from the Web UI is not compatible with the Core variants.
Comment #16
jonathan1055 commentedAll passed at previous versions
https://git.drupalcode.org/project/scheduler/-/pipelines/150255
Merged. Thank you for working on this. I will make a new release tomorrow.
Comment #17
jonathan1055 commentedI have released Scheduler 2.0.2
Comment #20
jonathan1055 commentedBackported to 8.x-1.x
https://git.drupalcode.org/project/scheduler/-/commit/28902d0e64f70894b3...