Subject: bug#75334: closed (Re: 500 error when running mumi compose)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 19 Feb 2025 21:08:03 +0000

Your bug report

#75334: 500 error when running mumi compose

which was filed against the mumi package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
75334: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75334
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: 500 error when running mumi compose
From: Arun Isaac <[email-masked]>
To: [email-masked]
Cc: Arun Isaac <[email-masked]>, jgart <[email-masked]>
Date: Wed, 19 Feb 2025 21:07:10 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

> I'll close this issue once I have deployed a new version of mumi with
> the guile-email fix.

The new version of mumi is now up. And, this issue seems to be no more.

Closing, thanks!

Subject: 500 error when running mumi compose
From: jgart <[email-masked]>
To: [email-masked]
Cc: Arun Isaac <[email-masked]>
Date: Fri, 03 Jan 2025 20:15:34 -0600
List-Id: <debbugs-submit.debbugs.gnu.org>

$ mumi compose --done
Backtrace:
           3 (primitive-load "/gnu/store/gbp28chjw8z9c8h3j8p4h7xrz03…")
In mumi/client.scm:
   529:30  2 (compose-email #:close? _ #:reply-to-spec _)
     89:2  1 (reply-email-headers 72926 #:reply-to _ #:include-body? _)
In kolam/http.scm:
    121:4  0 (graphql-http-response _ _)

kolam/http.scm:121:4: In procedure graphql-http-response:
GraphQL query failed with non-2xx status code: #<<response> version: (1 . 1) code: 500 reason-phrase: "Internal Server Error" headers: ((server . "nginx") (date . #<date nanosecond: 0 second: 1 minute: 12 hour: 1 day: 4 month: 1 year: 2025 zone-offset: 0>) (transfer-encoding (chunked)) (connection close)) port: #<input-output: string 7fdac3060930>> ""

Looks like something there is causing a 500 error.

WDYT
-- 
all the best,
jgart