AWS: don't refresh the page when contest phase changes #1510
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prandla
added a commit
to e-i-o/cms
that referenced
this pull request
Aug 17, 2025
prandla
added a commit
to e-i-o/cms
that referenced
this pull request
Aug 21, 2025
prandla
force-pushed
the
aws-no-refresh
branch
from
240ca5b to
be007f0
Compare
veluca93
approved these changes
Aug 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We frequently have a problem where the AWS service gets overloaded right at the end of a contest. I suspect this is because the client-side logic tries to refresh the page the instant the contest ends, when most jury members will have multiple tabs of AWS open (I usually end up with over 10...).
The phase of the contest is used solely to show the remaining time countdown. So instead I computed the phase in the countdown logic itself. This required duplicating the "current phase" logic from python to javascript, but I don't think it's a big deal, because half of this logic was duplicated in that javascript function already.