The server locked the scores. The judge’s screen still said “Update.”
Glassbox had a misleading screen at exactly the moment a judging platform needs to be clearest. An organizer published the results. The server correctly refused further score changes. But the judge’s page still looked editable. A judge could spend time revising a comment, press Update, and discover that the action had already become impossible. This turned up during the build’s browser…
The brief covers a situation where a server locked the scores during a judging process, but the judge's screen still showed the option to update. This issue was discovered during the development of Glassbox, an open-source server for submission and judging, which is used for DOGFOOD 2026. The fix involved a small code change that explicitly changed the state transition to both prevent further edits on the system and inform users accordingly.
The solution ensures that once the results are published, the system displays a locked notice, disables score fields, and removes save and recusal actions. This transition is crucial to prevent confusion and wasted effort for judges who might try to revise already-finalized scores.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
