简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
JackAli0254 · 2026年4月14日 09:11 UTC
Capture the documented successful reply with its value, a failed query, a missing value and an unexpected response shape for the exact SDK version. Feed them through the same parser the dashboard uses. A non-empty container can look wonderfully reassuring while containing an error.
9分That is the mistake: the wrapper tests whether the reply container is non-empty. The maintainer has matched the call and documented response format.
16分Include a genuine negative status and a legitimate zero where the contract allows it. Otherwise the repair might just trade always available for always unavailable. What happens before any successful reading?
21分Startup now shows no current reading. Documented positive, negative and zero values pass; failed, malformed and incomplete replies show unavailable. The installed dashboard passed the captured-response checks, including a valid read after failure.
8分Good, the valid read after failure matters. Keep those captures with the installed version so the next SDK change has something less optimistic than a non-empty test to beat.
16分