500 error when running mumi compose

  • Open
  • quality assurance status badge
Details
One participant
  • jgart
Owner
unassigned
Submitted by
jgart
Severity
normal

Debbugs page

J
J
jgart wrote 7 days ago
(address . bug-mumi@gnu.org)(name . Arun Isaac)(address . arunisaac@systemreboot.net)
87frlz9veh.fsf@dismail.de
$ 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
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOx1/GeNrtgwPWyyppSqitHe23TUFAmd4mcYACgkQpSqitHe2
3TW3/Q/+Nt3DMo5gcgYl7W6vNVte4M624TlOc8bBYRpg8CCAXUobbFkF3Utu3Vbn
nrsvTW+9puD88r+lBqk7ZEkGntLI/pYA0rGoW5SeN2m2ORRbO/Z0JFdVFWveYdth
t5Dn/G7SJi41G3lsmZaAMMmRcby3YKGFC2MdHc5Vi7mUVA+XK8AI1jhRCYEqRPsc
4j844ofY5gokl1pOp73Ps4kg6IMeNm1cVTFN4uXsIki5mPTWxfFi/jyWoR5j5F43
elND6V7K257bCHOdBm5sK09hoe2R93fmp0zWSR9BQqhcdgTHhJ3zuVf1c6++6SG8
zcRhqpOah6Gi7yfze1IYSQmMrGoZn86YMV/sFB6gZ0KH+TGgGtoLi61fLsp2+Ohf
rfHmuKxf9B8EHjXbrbv87aPrzhFqlta9OAdb+pVAjvoaIXI27eSbGZp+b72AI5LK
JExNGfFphO26ANqSfZ/bI/1zZsaUulmpxHcw15KkxCOAgK9Gq2ZPfO2lDg3Knacf
8NXY0ZkpKewx2aExYVICaMoHqTilHYJHNaCewuX0i1k4SAsokQXuqpJGWiahYxmm
u5DF4lWZU5BDDUD+ZvtOT7lPm8/oJlBP+J1/XsKDNlcMvFkclhlz6OU0Ep1zGPS0
pM8UXkkL/rGMDPfMgkB5s/+eRd0LY2Q/unxlEgzH7+j8wYnqgas=
=DzrH
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 75334@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 75334
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch