简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
LeoBrooks0797 · 2025年9月22日 18:50 UTC
At the result entry as well as the screen. Have you actually checked the stored result rows, or just the total shown in another window?
9分Actual rows. One accepted result for that job. Two entries in the display's little event list, one from each connection. The counter is the length of that list
21分Then stop treating that list as production quantity. It includes connection events dressed up as results. You can show a previously completed job after reconnect without counting another housing.
15分Lucy, would you hide the repeat in the event list? I'd leave it visible but say it was loaded again. Handy when somebody says the display jumped.
7分Leave the history visible. Give the reconnect entry different wording and build the quantity from accepted result records. And check whether job numbers can repeat after a restart before using the number alone as the key.
17分Counter now comes from the saved results in our replay test. The repeat entry says restored result. No extra housing counted there. Restart identity still needs answering before we call it fixed.
22分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .