From: jgart via Bug-mumi via "Bug reports for GNU Guix Mumi." <bug-mumi@gnu.org>
To: 75334@debbugs.gnu.org
Cc: Arun Isaac <arunisaac@systemreboot.net>
Subject: bug#75334: 500 error when running mumi compose
Date: Fri, 03 Jan 2025 20:15:34 -0600 [thread overview]
Message-ID: <87frlz9veh.fsf@dismail.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
$ 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
reply other threads:[~2025-01-04 4:01 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://issues.guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frlz9veh.fsf@dismail.de \
--to=bug-mumi@gnu.org \
--cc=75334@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=jgart@dismail.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).