Overarching project covering the Mailing Lists Phabricator application
Jun 5 2018
Jul 9 2017
Apr 3 2017
This is also not a valid feature request.
Could you reopen and set it as feature request?
This does not describe a bug in Phabricator.
Mar 8 2016
Sep 6 2015
Aug 31 2015
Jul 27 2015
Jul 26 2015
I worked around the update issue by using
git fetch git reset --hard 6be53bd9160807fb7c829b72b23025d233f7072c
(as suggested on the IRC)
Jul 21 2015
Jul 14 2015
I wish I had saved the logs, but alas.
Do you still happen to have the original error message? That was unexpected, and the migration specifically accounted for the case of email collisions and I recall testing that case locally in detail, so I'm curious what I missed. The expected behavior is that that list wouldn't migrate (and would emit a message), but other lists would:
Not sure the migration works as intended.
Jul 8 2015
Jun 11 2015
Jun 9 2015
Presuming resolved, yell if anyone's still running into issues.
Jun 8 2015
It's only issuing one statement so it will jump from 0% to 100% after adding the key, but it might take a bit if you have a lot of data in the table.
We saw a bunch of lines like:
Updated mailing lists in Herald action 1466.
I believe the error is now fixed at HEAD.
Jun 6 2015
I don't think this really matters if you've decided to fix the issue, but in case you're curious:
If you haven't run into it, T8398 has general context and guidance on this change. I've updated it to include the information here.
Worth adding: most of these were not intentionally created to refer to mailing lists. I think they used to just refer to plain email addresses, but then some migration in the past detected all of them, automatically created mailing lists for them, and automatically changed the Herald rules to refer to the mailing lists. So, I wouldn't be surprised if many installs run into similar issues.