DanLoop · 2025年12月20日 23:47 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
Does reconnect also request another check, or only change the total?
25分Show the maintainer the same completion before and after reconnect. A counter correction alone could leave the next connection ready to make the same mistake.
12分Only the total changes, Caleb; David, I can reproduce that with a saved event sequence without sending a new physical request.
11分Use that replay to test repeated reconnects. Once is too kind to it. Also include a retained completion whose identity cannot be matched; fixing this known coupon mustn't teach the app to quietly discard every awkward result.
15分Where did you see the extra count? On the display only, or in the exported inspection report too?
10分Gabriel, the unmatched result needs somewhere visible to wait for review.
3分Yes. Otherwise the operator gets a wonderfully calm screen while maintenance inherits a mystery later. Use wording that says what is unresolved, not another success colour.
10分Both display and export, Jonas; Gabriel, the replay now includes repeated reconnects and an unmatched retained result, with the latter kept visible outside the accepted total.
14分Does that state survive restarting the application as well? Reconnecting within one session might be using memory that the next startup won't have. I'd put both in the review before calling the reporting bug fixed.
6分Who will reconcile the unmatched result?
19分The revised replay passes both restart cases, Gabriel; Caleb, reconciliation still needs an agreed owner and procedure, so I have not handed this version over as finished.
21分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .