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 · 29 Aug 2025, 07:29 UTC
1 reply
Replying to FelixBaker0458
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.
21pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .