You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I, as well as some students working on CSC 517 projects, have noted that Expertiza seems to enforce deadlines a little late.
Specifically, this evening at 12:35 AM EST, my Scavenger Hunt code review assignment was shown as being in the review phase, but the "Others' work" links were still grayed. The submission phase was supposed to have ended at 4:55 AM UTC (11:55 PM EST). So reviewing should have been enabled.
I set the submission deadline back two days, and was able to see the review links.
What this indicates to me is that something is out of sync between the designation of the assignment as being in the Review phase and the graying of the "Others' work" link. I wonder if graying is running on EST, but the phase indication is running on UTC! If so, this would explain a lot about why deadlines don't seem to be enforced at the times they should.
The text was updated successfully, but these errors were encountered:
I think this is related to this issue. When I was trying to deploy a survey with the test database expertiza-scrubbed.sql and the current revision (cloned from the master 30 minutes ago), the time brought up in the popup time/date picker was the current date/time in EDT, but when I tried to submit the deployment it was enforcing a rule that the submitted time had to be in the future in UTC. Thus I had to advance the time I submit by at least 4 hours. The error message did not mention any timezones, so I had to guess as to what the problem was.
A move to a new version of Rails about a year ago caused many times to be
shown in UTC. That is unfortunate. It is not obvious where the offending
code is, though, and no one has had time to find and fix it.
In general, all deadlines need to be expressed in UTC.
I think this is related to this issue. When I was trying to deploy a
survey with the test database expertiza-scrubbed.sql and the current
revision (cloned from the master 30 minutes ago), the time brought up in
the popup time/date picker was the current date/time in EDT, but when I
tried to submit the deployment it was enforcing a rule that the submitted
time had to be in the future in UTC. Thus I had to advance the time I
submit by at least 4 hours.
Reply to this email directly or view it on GitHub: #38 (comment)
I, as well as some students working on CSC 517 projects, have noted that Expertiza seems to enforce deadlines a little late.
Specifically, this evening at 12:35 AM EST, my Scavenger Hunt code review assignment was shown as being in the review phase, but the "Others' work" links were still grayed. The submission phase was supposed to have ended at 4:55 AM UTC (11:55 PM EST). So reviewing should have been enabled.
I set the submission deadline back two days, and was able to see the review links.
What this indicates to me is that something is out of sync between the designation of the assignment as being in the Review phase and the graying of the "Others' work" link. I wonder if graying is running on EST, but the phase indication is running on UTC! If so, this would explain a lot about why deadlines don't seem to be enforced at the times they should.
The text was updated successfully, but these errors were encountered: