简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our FR5 display turns a failed response into a green status

RebeccaBaker0517 · 2025年9月18日 01:16 UTC

已关闭
RE
RebeccaBaker0517
We've paused using the diagnostic display for decisions. After the SDK change, a failed read can still produce a green status because the wrapper accepts the returned container as a value. Need the interpretation fixed, not another reassuring screen colour.

5 条回复

JO
JoAllen0331

Capture the successful and failed response structures for the installed SDK version. Have the wrapper check the documented success result before interpreting the payload. Add malformed responses to the offline cases as well.

16
RE
RebeccaBaker0517

Developer found a truth test on the whole response. Nonempty failure responses passed it. They've added explicit interpretation using the matching documentation and saved examples.

23
JO
JoAllen0331

Test a successful read followed by a failure. The old value may still be useful as last known, but its original update time must not become the failed request time.

10
RE
RebeccaBaker0517

That test found the timestamp moving on failure. Fixed now: unavailable for current status, retained value clearly dated. Initial failure has no made-up zero. Operator wording review is next.

7
JO
JoAllen0331

Did the operator review distinguish unavailable from last known without prompting? That is the remaining check I would want before relying on the display again.

13

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .