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

Our FR10 dashboard stayed green with a failed status request

WillChan1096 · 2025年4月21日 22:42 UTC

已关闭
WI
WillChan1096
I noticed our diagnostic screen reporting the same reassuring status after an SDK request failed. The new library returns a container where the old wrapper expected a value. Has anyone dealt with the display side of this, especially what the operator sees while no fresh answer is available?

6 条回复

SO
SofiaBell0630

What does the screen do with the previous value? I'd want it visibly stale, with its age, so nobody reads a perfectly green box as a fresh answer while they're trying to sort a stoppage.

4
WI
WillChan1096

It keeps the value and loses the failure information. We have checked the installed SDK's return format and are fixing the wrapper. The old screen gives no age indication either.

18
SO
SofiaBell0630

That's quite a cheerful screen you've got. Can you feed the revised display saved success and failure responses to see what an operator will actually get?

20
DA
DanielAbbott0043

Try an empty or oddly shaped reply as well, because ours managed to turn a missing value into zero and zero happened to mean everything was fine. Nobody enjoyed that discovery.

2
SO
SofiaBell0630

Did you show the new version to someone on shift? Curious whether 'unavailable' and 'last known value' are clear when they're standing at the bench, rather than us staring at the code

21
WI
WillChan1096

Yes. They preferred the current status to say unavailable, with the last good value and age underneath. Failed and malformed responses now show that state in our checks. We have kept the detailed error available for maintenance.

5

讨论已关闭

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