https://bugzilla.wikimedia.org/show_bug.cgi?id=71858
--- Comment #2 from Matthew Flaschen <mflasc...@wikimedia.org> --- Erik suggested having UserTuple enforce a valid state. I think this can be done in the constructor. That will then hopefully reveal what is creating bogus UserTuples (since it will throw before it makes it to the database). This may require changing IRCLineUrlFormatter to not construct mock workflows (the UserTuple logic can't be air-tight if there is an exception for this (as there currently is). We also need to figure out what to do with the already-corrupt data on the test wiki. Simplest solution is probably to assign it to someone manually. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
