[Mailman-Developers] Fwd: Mailman | The unsubscribe process using the -leave address does not work because of an `assert` in the code (#310)

[Barry Warsaw]

On Feb 09, 2017, at 07:38 AM, Mark Sapiro wrote:

>@abompard I don't know what's going here. I received the notice below from
>GitLab. I tried to go there to comment that this looks like a duplicate or at
>least very similar to <https://gitlab.com/mailman/mailman/issues/294> which
>was fixed about 3 weeks ago, but GitLab gives me a 404 and says there is no
>issue #310.

I'm not positive, but I have a theory.  GL says there are only 309 issues of
both closed and open state on the mailman project.  It's possible that this
one got caught up in their database incident:

https://about.gitlab.com/2017/02/01/gitlab-dot-com-database-incident/

and the email was queued up before then, since it's date of 09-Feb-2017 is
well after the incident was resolved.  It's known that about 6 hours of
issues, MRs, comments, etc. were irretrievably lost.

I did move an issue from mailman to postorius, but I believe that what happens
in that case is that a new issue is created in the target project (with
duplicate contents but a different issue number in sequence with the target),
while the source project's issue just gets closed.  I can't find that one
right now to confirm.

Anyway, Aurelien would probably need to say whether his issue falls within the
timeline of the GL database snafu or not.  I think there's no option but to
try to re-submit the issue if that's the case.

Cheers,
-Barry