GNU bug report logs - #70613
Report GraphQL error when queried for non-existent bug

Previous Next

Package: mumi;

Reported by: Arun Isaac <arunisaac <at> systemreboot.net>

Date: Sat, 27 Apr 2024 19:20:02 UTC

Severity: normal

To reply to this bug, email your comments to 70613 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-mumi <at> gnu.org:
bug#70613; Package mumi. (Sat, 27 Apr 2024 19:20:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Arun Isaac <arunisaac <at> systemreboot.net>:
New bug report received and forwarded. Copy sent to bug-mumi <at> gnu.org. (Sat, 27 Apr 2024 19:20:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: bug-mumi <at> gnu.org
Subject: Report GraphQL error when queried for non-existent bug
Date: Sat, 27 Apr 2024 20:18:23 +0100
When the mumi GraphQL endpoint is requested for a non-existent bug, it
should provide a clear error message in the response. At the moment, it
merely fails with an "Internal Server Error", and the user is left
groping in the darkness.

Here's a minimal failing example:

--8<---------------cut here---------------start------------->8---
(use-modules (kolam http)
             (ice-9 pretty-print))

(define %graphql-endpoint
  "https://issues.guix.gnu.org/graphql")

(pretty-print
 (graphql-http-get %graphql-endpoint
                   '(document
                     (query (#(issue #:number 2)
                             number
                             title
                             date
                             open)))))
--8<---------------cut here---------------end--------------->8---




This bug report was last modified 1 year and 50 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.