(Moving epriestley to Bcc)
Yes, this is a known issue and is being tracked at
https://phabricator.wikimedia.org/T91488
Sorry for the noise in your mailboxes. We hope to be able to clean up your
tasks.
On Wed, Mar 4, 2015 at 11:24 AM, Petr Kadlec <petr.kadlec(a)gmail.com> wrote:
Hi,
somebody probably already noticed this, but I didn’t see any discussion
around, so just to be sure:
I have received notifications about commits being assigned to old bugs in
Phabricator by epriestley. See for instance T4123 [1] – “epriestley added a
commit: Unknown Object (Commit)”.
It seems to me the problem is that somehow the Wikimedia instance of
Phabricator and the Phabricator instance of Phabricator (erm… the Phacility
instance?
secure.phabricator.org, I mean) got
crossed/synchronized/whatever. Therefore their commit D7601 [2], marked as
fixing _their_ bug T4123 [3] somehow modified _our_ bug T4123. [1] It might
have been helped by the fact Evan Priestley has the same “epriestley”
account at both installations.
While adding nonexistent commits makes a bit of a mess, it’s not a huge
problem, but some of these commits changed state of the underlying task as
well, which is worse. See epriestley’s feed [4]. I guess those would need
to be reverted?
-- [[cs:User:Mormegil | Petr Kadlec]]
[1]:
https://phabricator.wikimedia.org/T4123
[2]:
https://secure.phabricator.com/D7601
[3]:
https://secure.phabricator.com/T4123
[4]:
https://phabricator.wikimedia.org/p/epriestley/feed/
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil