Page MenuHomePhabricator
Create Task
Maniphest T11503

Notifications for past events sent after Phabricator upgrade
Closed, DuplicatePublic
Actions

Description

We recently upgraded our Phabricator following the guidelines on this page.

https://secure.phabricator.com/book/phabricator/article/upgrading/#upgrade-process

Ever since the update, users are reporting they are receiving email notifications for commits and changes made 6+ months ago. Is there some way of resetting notifications?

Reproduction Steps:

  1. Stop all phabricator services (web, phd, aphlict)
  2. Update all files (phabricator, arcanist, libphutil)
  3. Perform database update
  4. Start services

Expected behavior

Users will receive email notifications for changes made after the update

Actual behavior

Users are receiving emails for previous commits and changes 6+ months ago

Version
phabricator 34af66122e47f3194156847e36e583b5d67cfcda (Mon, Aug 15)

Troubleshooting steps taken

  • Restarted phd
  • Looked at web error logs
  • Looked at phd daemon logs

Related Objects

Event Timeline

jessjohnson created this task.Aug 20 2016, 1:14 AM
jessjohnson updated the task description. (Show Details)
chad added a subscriber: chad.Aug 20 2016, 1:29 AM

This is expected, as they are most likely not previously discovered commits.

chad added a comment.Aug 20 2016, 1:40 AM

Well, I'm guessing overall, roughy my theory is:

  • It's been a while since you've updated
  • These commits are ones not previously imported into Phabricator.

Outside of those guesses, it would be helpful to have a full set up steps to reproduce the issue. The steps you've provided aren't complete enough for me to reproduce the issue you may be seeing.

chad edited projects, added Bug Report (Needs Information), Diffusion; removed Bug Report.Aug 20 2016, 1:41 AM
epriestley added a subscriber: epriestley.Aug 20 2016, 2:16 AM

Yeah, this is likely the same as T11188. See that task for some additional discussion.

jessjohnson added a comment.Aug 20 2016, 4:14 AM

Yes, this seems to be exactly what the other issue was referring to. We've just recently upgraded (previous codebase was 2+ years old) and massive amounts of commit email are getting sent out.

I will try to put the repositories in an importing state to calm down the mail volume (command referenced in the above issue).

epriestley closed this task as a duplicate of T11188: Updating to latest Phabricator caused feed corruption.Aug 20 2016, 10:55 PM
Phabricator · Built by Phacility