Unhandled exception muting (completed?) bulk jobs


Observed Behavior:
Unhandled exception after clicking mute on a bulk job.

Unhandled Exception (“PhabricatorApplicationTransactionStructureException”)

Attempting to apply a transaction (of class “PhabricatorWorkerBulkJobTransaction”, with type “core:edge”) which has not been constructed correctly: Transaction has type “core:edge”, but that transaction type is not supported by this editor (PhabricatorWorkerBulkJobEditor).

Expected Behavior:
There should probably not be an unhandled exception?

Phabricator Version:
Installed Versions
5d88eef26b72623be528f6e448b5615a7cb166c2 (Sat, Feb 23) (branched from 701a9bc339b9d419326a62e85ef13666b08046cd on origin)
b4a302683b1aefbbb2ab9d1aaaf418b551b84b28 (Sat, Feb 23) (branched from 9581dd0f52726b10c923038c28d5fe2170f0d1b6 on origin)
813a26a2d09758f3c407a0c99c6761f11f62cb90 (Sat, Feb 23) (branched from 671ec8fb8f7aa74e9e825ca95fd96ce4bbf79160 on origin)
3.3 at /usr/bin/diff
2.1.4 at /usr/bin/git
Not Available
2.0.1 at /usr/bin/pygmentize
1.8.10 at /usr/bin/svn

Reproduction Steps:
Run a bulk job, then navigate to /daemon/bulk and select the job. After getting to the view/id page, click mute on the right side and click mute again to confirm it.

Or, go to this test instance and click mute.


Thanks, see https://secure.phabricator.com/D20226.

(Note that subscribe/mute only affect notifications about edits to the " Bulk Job" object itself, not notifications the job creates by editing other objects.)



edit: thanks for the clarification on what it actually does, although I didn’t really care either way. I was mostly just fiddling around with the UI and I figured unhandled exceptions were probably bad no matter what the effect was actually supposed to be (at least until you add a button somewhere that says “make phabricator fatal” and then i click it)

closed #4