In T175146, we decided to move infrastructure for running jobs into MediaWiki core. There's one module that is part of the EventBus extension, SpecialRunSingleJob. Like the rest of the job-running infrastructure, it should be moved to core.
Description
Related Objects
- Mentioned Here
- T175146: JobQueue: Unify JobRunner entry points
Event Timeline
It seems the "Special:RunSingleJob" code is currently unused. Is it obsolete? Is it something new we need in addition to other five (!) jobrunner entrypoints? Or is it something else?
From a quick look through its history, it seems like it might be an incomplete porting of the wmf RPC entrypoints (from T175146) to a Special implementation, which presumably (once finished and independent), would be moved to core. If that is indeed the case, then it exists only temporarily in EventBubs and this task would a duplicate of that.
In its current form the two separate tasks existing suggest we are planning to both move the wmf-rpc endpoints and this EventBus special page to core, which I think would be a mistake. That would leave core with six (!) distinct jobrunner entrypoints. It currently has three, and I was expecting part of T175146 to "fold two wmf/rpc endpoints" into core by improving or replacing the ones it has.
(3 in core: SpecialRunJobs, maintenance/RunJobs, and post-send job running)
(2 in wmf/rpc: RunJobs, RunSingleJob)
(1 in mwext/EventBus: SpecialRunSingleJob)
Oh, I was somehow not aware of this task existence.
The Special:RunSingleJob was an initial attempt to implement what's suggested in T175146 via a REST endpoint in EventBus extension. https://gerrit.wikimedia.org/r/c/mediawiki/extensions/EventBus/+/571816 is cleaning up (removing) this special.
To answer @Krinke - no, we don't need six. As a part of the current work wmf/rpc endpoints will be removed as well, so we will be down to 4. I will document these after the current overhaul and we can look if it would be possible to cut some more.
I'm closing this task as invalid.