Gracefully handling all nix evaluation failures. #464

New Issue

hsjobeki · 2023-11-04T12:27:51Z

hsjobeki commented

2023-11-04 12:27:51 +00:00

Currently many nix runtime / evaltime failures result in "Internal Server Error 500"

We should at least catch all those errors and gracefully report them without crashing the server.

Ideally every endpoint should handle its own errors, but we should implement some "catch all" generic failure, if the specific endpoint has no specific error handling yet.

Currently many nix runtime / evaltime failures result in "Internal Server Error 500" We should at least catch all those errors and gracefully report them without crashing the server. Ideally every endpoint should handle its own errors, but we should implement some "catch all" generic failure, if the specific endpoint has no specific error handling yet.

Qubasa was assigned by hsjobeki

2023-11-04 12:27:59 +00:00

DavHau was assigned by hsjobeki

2023-11-04 12:28:04 +00:00

DavHau commented

2023-11-10 09:17:27 +00:00

This is now fixed for the schema endpoint, but there is no generic mechanism in place that ensures this for all evaluations. We might want to make a nix_eval function which always throws the correct error internally.

This is now fixed for the schema endpoint, but there is no generic mechanism in place that ensures this for all evaluations. We might want to make a `nix_eval` function which always throws the correct error internally.

👍 1

DavHau closed this issue

2023-11-13 14:42:48 +00:00

Sign in to join this conversation.