unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Arun Isaac <arunisaac@systemreboot.net>, guix-devel@gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: `mumi send-email' means no more debbugs dance to send multiple patches
Date: Tue, 25 Apr 2023 18:26:52 +0200	[thread overview]
Message-ID: <87ttx4rkqb.fsf@jpoiret.xyz> (raw)
In-Reply-To: <874jp4i1vu.fsf@systemreboot.net>

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

Hi Arun,

Arun Isaac <arunisaac@systemreboot.net> writes:

> Hi Josselin,
>
> Ouch! Unfortunately, timeouts can happen. I was just hoping it would be
> unlikely. Did you wait out the full 15 retries of `mumi send-email'?

Yes, I did wait until it completely timed out.

> This is admittedly a somewhat fragile system, but it is the best we can
> do considering debbugs' limitations. Given email's asynchronous store
> and forward design and all the polling we do, a `mumi send-email'
> timeout is possible. Do you think increasing the number of times `mumi
> send-email' retries would help? Did the email you sent using `mumi
> send-email' finally reach debbugs and the mumi server? How long did it
> take? How long do your emails typically take to reach debbugs and the
> mumi server?

My mails usually take less that 30 seconds to get a reply from debbugs.
I don't remember how long it took yesterday for the issue to appear on
mumi though, but more than the 15 retries of mumi send-email (I manually
checked).

> Thanks for the feedback, and happy hacking! :-)

Thanks for your tool!

Best,
-- 
Josselin Poiret

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]

  parent reply	other threads:[~2023-04-25 16:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 15:12 `mumi send-email' means no more debbugs dance to send multiple patches Arun Isaac
2023-04-24 18:17 ` (
2023-04-24 20:08 ` Josselin Poiret
2023-04-25 12:26   ` Arun Isaac
2023-04-25 14:44     ` Ricardo Wurmus
2023-04-26 23:51       ` Arun Isaac
2023-04-25 16:26     ` Josselin Poiret [this message]
2023-04-26 23:57       ` Arun Isaac
2023-04-27  8:49         ` Josselin Poiret
2023-05-01 23:37           ` Arun Isaac
2023-04-26 10:12 ` Andreas Enge
2023-04-27  0:33   ` mumi web server bugs [was "`mumi send-email' means no more debbugs dance to send multiple patches"] Arun Isaac
2023-04-26 21:27 ` `mumi send-email' means no more debbugs dance to send multiple patches John Kehayias
2023-04-27  0:08   ` Arun Isaac
2023-04-28 13:59     ` Maxim Cournoyer
2023-05-01 22:47       ` Arun Isaac
2023-05-02 12:41         ` Maxim Cournoyer

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=87ttx4rkqb.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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).