When configuration was modified, e.g. by extensions during the initialization phase, we need to reset all service instances to ensure they are all consistent with each other, and are all based on the latest version of the configuration. However, such a reset may be expensive - we may end up re-loading bulk data, or re-establishing network connections.
To avoid resetting expensive services, we should be able to blacklist them, so any attempt to reset them would fail.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | daniel | T384 RfC: Dependency Injection for MediaWiki core | |||
| Resolved | daniel | T124792 RFC: Service Locator for MediaWiki core | |||
| Open | None | T132708 Allow blacklisting services against a "quick" service reset. |
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)