We have about 30~ tasks with this worker name, even though it looks like it was renamed to "DoorkeeperJIRAFeedWorker". These constantly fail because the worker class no longer exists. There probably a missing DB migration script to deal with this?
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T3554 Implement a `bin/worker kill <criteria>` for batch-flushing tasks from the queue | ||
| Duplicate | epriestley | T7079 Implement `bin/worker purge` or similar to destroy tasks with unknown task classes |
Event Timeline
Comment Actions
For installs with phabricator.developer-mode disabled, we could conceivably fail tasks with a missing class permanently, although I'm hesitant about that (it's possible that they're important and the administrator just uninstalled an extension by accident).
I'd rather do something like bin/worker burn to destroy everything with a bunch of failures and just plaster that with warnings, maybe.