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

Why has changing the FR10 SDK made failed polls look believable?

ReeceAbbott0036 · 2026年6月9日 14:45 UTC

回复讨论
RE
ReeceAbbott0036
I need to repair the status wrapper before using this dashboard again. The replacement SDK returns a container where the old version supplied the value we expected, and a failed request can now appear to contain valid status. I have preserved examples of both response types.

7 条回复

JO
JonasArcher0372

What does the screen show after failure? Please don't leave the previous value looking current while you fix the decoder.

18
RE
ReeceAbbott0036

It currently leaves the old value visible. I have marked the dashboard unavailable while I work through the saved responses; the operator display should not invite guesses.

14
RE
RebeccaBarnes0604

How are you identifying which SDK contract applies? Folder name, version metadata, something else? I wouldn't know which container to trust from its appearance alone.

9
RE
ReeceAbbott0036

I have recorded the imported module path and version on each laptop. This installation only needs the replacement version, so I can make that dependency explicit in the wrapper.

5
JO
JonasArcher0372

Did the failure examples get a separate display state? Interested whether a failed read still leaves anything that looks usable.

24
RE
ReeceAbbott0036

Yes, the local checks now show unavailable and a last-success timestamp. Success status is decoded only after the documented success condition and response shape pass. Malformed and unfamiliar values also remain unavailable.

13
RE
RebeccaBarnes0604

What happens on a connection that stays open but stops delivering fresh data? That's the remaining case I'd ask about before calling the screen reliable.

18

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。