Our read-only dashboard uses a wrapper that expected one value. The replacement client environment returns a container, and the wrapper now extracts something plausible even when the request failed. What should the boundary check before the display is allowed to call it a current reading?
How should the UR5e wrapper reject an unsuccessful status response?
FelixBaker0458 · 2025年8月29日 07:29 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
1 条回复
Have the software owner use the installed interface's documented success and data fields, and reject failed or malformed responses before publishing a status; I'd also test a failure immediately after a good reading, because the old value staying on screen can hide a perfectly real error.
21分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .