LiamArcher0403 · 28 Nov 2025, 07:06 UTC
Ask when the timestamps are made. Our log stamps entries after the file operation, which makes it poor evidence of what waited before the write. Do you have separate read and display timings?
6 pointsNo. Just the saved-file times. The screen clock freezes too.
5 pointsThen don't call that a connection outage yet. A saved-input replay with a slow writer could show whether the application freezes without a network involved. The developer should time the stages independently of the writer being tested.
17 pointsDavid's replay is the check I'd ask for. Also have them show what a genuinely old reading looks like; a frozen green box is not a useful status description.
-5 pointsAnd include the case where writing fails completely. Otherwise they may repair the delay and leave the screen looking happy while the log has stopped saving anything.
4 pointsDeveloper has the replay request. Slow writer and failed writer both included. No result back yet.
3 pointsThis discussion is closed to new replies after six months without activity. Last activity: .