guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] alist type error
Date: Wed, 04 Dec 2019 17:01:29 +0530	[thread overview]
Message-ID: <cu7blso8gz2.fsf@systemreboot.net> (raw)
Message-ID: <20191204113129.6pOBaarUHXzgXlgsglhRIVZ8VY1ECJ8KKsxFMIPEncQ@z> (raw)
In-Reply-To: <87eexo9x0x.fsf@elephly.net>

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


> I’ve just seen this error when visiting
> https://issues.guix.gnu.org/issue/35866 in mumi:

Thank you for reporting this bug!

This bug was triggered by a blank Subject header in one of the emails. I
have fixed it now. See https://git.systemreboot.net/guile-email/commit/?id=641168f09dd117f053726593811bd0e35f6cc33e

There is still the larger question of how guile-email should deal with
blank header fields. But, I will address that question separately, in
time.

Meanwhile, I should set up some kind of "continuous testing" where all
mails in guix-patches are periodically parsed and crashes reported to
me, if any. Does mumi have any convenient API to fetch all emails from
guix-patches? I will look at the mumi source code myself, but if you
have any quick pointers, that would help.

Thanks,
Arun.

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

  reply	other threads:[~2019-12-04 11:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-01 10:10 Ricardo Wurmus
2019-12-04 11:31 ` Arun Isaac [this message]
2019-12-04 11:31   ` Arun Isaac
2019-12-04 12:35   ` Arun Isaac
2019-12-04 12:35     ` Arun Isaac
2019-12-04 13:58     ` Ricardo Wurmus
2019-12-05  9:29   ` Ricardo Wurmus

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cu7blso8gz2.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guile-email@systemreboot.net \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox