GNU bug report logs -
#74395
'mumi send-email' fails to detect created issue number
Previous Next
Full log
View this message in rfc822 format
Hi,
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hello,
>
> I've been using 'mumi send-email', and one annoyance is that it doesn't
> seem to reliably (or at all?) detect the created issue in the tracker,
> even after the issue was synced to the MUMI database and visible through
> the web interface.
>
> For example, the issue https://issues.guix.gnu.org/74394 took about 3
> minutes to be processed by GNU Debbugs and was available in the web
> interface of Mumi, while the 'mumi send-email' client kept printing:
>
> Server has not yet received our email. Will retry in 60 seconds. 14 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 13 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 12 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 11 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 10 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 9 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 8 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 7 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 6 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 5 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 4 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 3 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 2 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 1 retries remaining.
> Server has not yet received our email. Will retry in 60 seconds. 0 retries remaining.
> Mail not acknowledged by issue tracker. Giving up.
>
> It'd be nice to investigate and fix that.
The reason is that mumi on the server side attempts to reindex the
complete 20 GiB something of mail archives every 5 minutes, which takes
20 minutes to complete.
We need a finer grained mechanism to process only newly added mails and
avoid doing a full reindex, which is too costly.
--
Thanks,
Maxim
This bug report was last modified 60 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.