Our old status wrapper expects a value; replacement SDK returns a container. Failed UR5e reads now get normal labels. Where should validation happen?
UR5e status container reaches our display even when the request failed
ElenaAdams0166 · 2026年8月16日 03:29 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
4 条回复
At the adapter boundary, using the applicable response contract to distinguish request success from validated status data; test malformed replies and good-read-then-failure before the screen updates.
10分Contract located for this environment. Maintainer has the failed container example and a good-then-failure test. No code correction completed yet.
24分Also include a genuine valid status that is not favourable. The adapter should not turn every negative-looking reading into a communication failure. Preserve the distinction between unavailable data and an observed condition.
6分Offline cases now pass after the repair, including valid negative status and stale previous data. Supported-environment comparison remains outstanding. The training display is not released yet.
11分