Page MenuHomePhabricator

Consider modifying H153 to reduce mass task spam
Closed, ResolvedPublic

Description

H153 looks like it's been mis-configured (from what I can tell without admin access).

I think it's meant to add @TerraCodes to new tasks which are in "ArticleRatings, Brickimedia, DeepSea, Discussion-modeling, Dumps-Generation, FR-Campaigns, GlobalContribs, Increasing-content-coverage, MediaWikiChat, NewTalkGlobal, NumberOfComments, PAWS, Refreshed, Reports-bot, Snippet, Splash, Timeless, USERNAME, WMUA-Community-Support, WMUA-Contests, WMUA-Partnerships, WMUA-Tech, Wikimedia-DC, procurement (!)", but instead it's doing an OR on the conditions and a NOT on the list of projects – so they get CCed on any new task, and any task not in that odd list of projects when it's edited.

Can the user disable it, or failing that, a Phabricator admin do so?

Related Objects

Event Timeline

Access policy is set to no one, so it requires server admin intervention (normal phab admin can't help)

Access policy is set to no one

This is default for private rules, you can't change it. We have three possible ways:

  • a) Wait for @TerraCodes and let him fix this
  • b) delete the rule via sudo ./bin/remove destroy H153
  • c) disable the account @TerraCodes (Stops the rule, but I think this is a bad possibilty)
  • d) correct the rule via UPDATE TABLE at the DB (maybe dangerours).

For this Case the DB query should be:

USE phabricator_herald;
UPDATE herald_rule
SET mustMatchAll = 1
WHERE id = 153;

(I'm 99,9% sure that this is the right query, but if you want to use it, 4 eyes controlling the query are better than 2 ;))

I think that I'm going to go with

c) delete the rule via sudo ./bin/remove destroy H153

Because I'd rather not execute arbitrary SQL in the production phabricator database.

But thanks @Luke081515 for going to the trouble to figure out the query!

This object will be destroyed forever:

    - H153 (HeraldRule) H153 TerraCodes' stuff


    Are you absolutely certain you want to destroy this object? [y/N] y

Destroying objects...
Destroying HeraldRule H153...
Permanently destroyed 1 object.

@TerraCodes: you may recreate your herald rule if you would like but please limit the auto-subscription to a focused list of tags you are actively working on.

The rule was meant to subscribe me to any newly created task that was not in those groups. (It was based off H9) On another note, is there a way to be emailed when someone mentions me, because Phabricator never told me about this and I only found this because I was left a message on MediaWiki. (And I only knew about the message due to Enhanced notifications telling me on enwiki)

The rule was meant to subscribe me to any newly created task that was not in those groups. (It was based off H9) On another note, is there a way to be emailed when someone mentions me, because Phabricator never told me about this and I only found this because I was left a message on MediaWiki. (And I only knew about the message due to Enhanced notifications telling me one enwiki)

There should be a setting in https://phabricator.wikimedia.org/settings/panel/emailpreferences/

The rule was meant to subscribe me to any newly created task that was not in those groups. (It was based off H9) On another note, is there a way to be emailed when someone mentions me, because Phabricator never told me about this and I only found this because I was left a message on MediaWiki. (And I only knew about the message due to Enhanced notifications telling me on enwiki)

There should be a setting in https://phabricator.wikimedia.org/settings/panel/emailpreferences/

If it exists, I can't find it.

The rule was meant to subscribe me to any newly created task that was not in those groups. (It was based off H9) On another note, is there a way to be emailed when someone mentions me, because Phabricator never told me about this and I only found this because I was left a message on MediaWiki. (And I only knew about the message due to Enhanced notifications telling me on enwiki)

There should be a setting in https://phabricator.wikimedia.org/settings/panel/emailpreferences/

If it exists, I can't find it.

There is not a separate notification type for that. I can't see anything related in upstream's phabricator instance (except the somewhat related https://secure.phabricator.com/T9031 )

The current system, relies upon the user reading all their email/notifications, and noticing @mentions.
If a user is not already subscribed to a task, then the @mention will subscribe them, and that serves as the notification.

You (@TerraCodes) are probably deluged in email, because (1) of all the projects that you are "watching", and (2) because of all the tasks that you're subscribed to due to the accidental Herald misconfiguration.
I strongly recommend that you stop "watching" any project you're not actively involved with.
I don't know what the best solution is, to fix the accidental subscriptions... (the only solutions I can think of are: (a) a new Herald rule to unsubscribe you from everything, as each task slowly comes up again, or (b) a bulk-edit of all tasks you're subscribed to (which would cause an email deluge for many other people, so is not good). Phab-wranglers, is there a better solution?

The rule was meant to subscribe me to any newly created task that was not in those groups. (It was based off H9) On another note, is there a way to be emailed when someone mentions me, because Phabricator never told me about this and I only found this because I was left a message on MediaWiki. (And I only knew about the message due to Enhanced notifications telling me on enwiki)

There should be a setting in https://phabricator.wikimedia.org/settings/panel/emailpreferences/

If it exists, I can't find it.

There is not a separate notification type for that. I can't see anything related in upstream's phabricator instance (except the somewhat related https://secure.phabricator.com/T9031 )

The current system, relies upon the user reading all their email/notifications, and noticing @mentions.
If a user is not already subscribed to a task, then the @mention will subscribe them, and that serves as the notification.

You (@TerraCodes) are probably deluged in email, because (1) of all the projects that you are "watching", and (2) because of all the tasks that you're subscribed to due to the accidental Herald misconfiguration.
I strongly recommend that you stop "watching" any project you're not actively involved with.
I don't know what the best solution is, to fix the accidental subscriptions... (the only solutions I can think of are: (a) a new Herald rule to unsubscribe you from everything, as each task slowly comes up again, or (b) a bulk-edit of all tasks you're subscribed to (which would cause an email deluge for many other people, so is not good). Phab-wranglers, is there a better solution?

I actually don't get email from phabricator because my notification settings are set to either ignore or notify for manifest tasks.

(2) Email Preferences.png (264×558 px, 31 KB)
Also, as far as I know all projects that I am watching, I watched before I made the herald rule. The only problem with creating a herald rule to unsubscribe me from all the tasks I'm subscribed to is that I have subscribed to some tasks that I would like to stay subscribed to. Also, is there a way to see what tasks and/or groups/projects that I am subscribed to?

@TerraCodes Oh, right, my mistake, I forgot about web-notifications (I disable them all).
You can search for

HTH.

@TerraCodes Oh, right, my mistake, I forgot about web-notifications (I disable them all).
You can search for

HTH.

Do you think it would be a good idea to get 'Batch Edit' permissions so that I can remove myself as subscriber from all the tasks I don't want to be subscribed to?

@TerraCodes: Your Herald rule apparently is still active, so you should disable (IIRC "archive") it before doing anything else.

Do you think it would be a good idea to get 'Batch Edit' permissions so that I can remove myself as subscriber from all the tasks I don't want to be subscribed to?

I don't think 'batch edit' permissions would be given for a one-time-use thing like this.
It's probably best to just unsubscribe from tasks you're not interested in, one-by-one, as they come up in your notifications.
This would help prevent other users from being inundated with update-notifications, if they have the preference for "A task's subscribers change." turned on.

It's probably best to just unsubscribe from tasks you're not interested in, one-by-one, as they come up in your notifications.
This would help prevent other users from being inundated with update-notifications, if they have the preference for "A task's subscribers change." turned on.

I'd prefer to be inundated with a huge batch of notifications that I can read all at once, rather than having them scattered among interesting ones.