GNU bug report logs -
#75334
500 error when running mumi compose
Previous Next
Reported by: jgart <jgart <at> dismail.de>
Date: Sat, 4 Jan 2025 02:17:02 UTC
Severity: normal
Done: Arun Isaac <arunisaac <at> systemreboot.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
$ 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
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 88 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.