mumi GraphQL endpoint errors out on non-existent issues

  • Open
  • quality assurance status badge
Details
2 participants
  • Arun Isaac
  • Felix Lechner
Owner
unassigned
Submitted by
Arun Isaac
Severity
normal

Debbugs page

Arun Isaac wrote 2 years ago
(address . bug-guix@gnu.org)
87y1kw6wne.fsf@systemreboot.net
The mumi GraphQL endpoint errors out with an "Internal Server Error"
when queried for an issue that does not exist. It should error out with
a meaningful error response.
Felix Lechner wrote 1 years ago
(no subject)
(address . control@debbugs.gnu.org)
87h6ii6d58.fsf@lease-up.com
reassign 65858 mumi
reassign 65809 mumi
reassign 49295 mumi
reassign 64833 mumi
reassign 54204 mumi
reassign 68920 mumi
reassign 55765 mumi
reassign 65923 mumi
reassign 63507 mumi
reassign 60226 mumi
reassign 63936 mumi
reassign 60951 mumi
reassign 66027 mumi
thanks
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 63936@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 63936
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
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help