From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 74395@debbugs.gnu.org
Cc: Arun Isaac <arunisaac@systemreboot.net>
Subject: bug#74395: 'mumi send-email' fails to detect created issue number
Date: Sun, 17 Nov 2024 21:21:04 +0900 [thread overview]
Message-ID: <871pzaf3v3.fsf@gmail.com> (raw)
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:
--8<---------------cut here---------------start------------->8---
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.
--8<---------------cut here---------------end--------------->8---
It'd be nice to investigate and fix that.
--
Thanks,
Maxim
reply other threads:[~2024-11-17 12:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871pzaf3v3.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=74395@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).