The issue may be more general than the new title, but this is more actionable (I think).
Note that I don't work for Phacility.

T9412 might be helpful in understanding this in the future.

You're getting this cause a task was merged, not because of the changed subscribers. The logic roughly looks like if (get mail for any reason) { send entire email; }. If you look at the full headers you should see a list of 'mail-tags'. If you're notifications are set to email for any one of those tags you'll get the email.

https://secure.phabricator.com/book/phabricator/article/notifications/ needs to be modified to fit the new world.

We do this as a minor extension to the typical 'land' workflow. That is we have a wrapper that causes 'arc land' to be equal to 'arc diff -m "automated bump" && arc land'. We do this so that the latest version in differential maps exactly to the one that got landed. This also always causes a comment to be created immediately before land. We could possibly work around this locally by comparing the diff in differential (with getdiff or the modern equivalent) but it would be amazing if we could just tell phabricator "we're attempting to update but don't generate a new transaction if its exactly the same).

@areitz FWIW, we use monit's ability to search for a process name. This isn't ideal but its the best we've come up with without forking the daemon code.

phoenix (like Greece)? phranks?

@CodeMouse92 consider duplicating on a phacility test instance.

Should I file a separate task for the general feature request?

Unsure if fits into this task or not but with only a single auth provider enabled for login it would be nice if it were transparent (and got automatically selected) rather than requiring the user to press a button.

In T10775#169974, @clemvangelis wrote:

Sorry, I read the "Describing Root Problem" and I thought that explaining the main problem (not intuitive for users and lack of visibility for Assigned to and Authored By) was sufficient.
The problem is that users ( at least ours) want to find all essential information (and assigned to seems to be an essential information) in the same place by taking a quick look at the task such as for priority and status.

Ah, I see. In my world master promotion independently of the web tier. The web hosts connect over a VIP which always reaches the current master. We can also connect over a VIP to reach the slaves but don't currently use this.

will this task support setting a separate read-only username and password for database connections? This is useful in our environment to access the slaves.