Distinguish empty checks results from checks request or parse failures #432

New issue

Closed

opened 2026-04-26 23:33:02 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-04-26 23:33:02 +00:00

Problem

The checks picker still logs no checks found when the underlying checks request fails or returns invalid JSON. That misclassifies real request/parse errors as an empty result and hides the useful failure details.

Proposed solution

Make the checks picker treat an actual empty checks list as "no checks", but preserve and surface real request/decode failures as warnings or errors with the underlying details.

Notes

root tracker: #170

## Problem The checks picker still logs `no checks found` when the underlying checks request fails or returns invalid JSON. That misclassifies real request/parse errors as an empty result and hides the useful failure details. ## Proposed solution Make the checks picker treat an actual empty checks list as "no checks", but preserve and surface real request/decode failures as warnings or errors with the underlying details. ## Notes - root tracker: #170