Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

At start, ScoringService could score/token the same submission twice #31

Closed
lw opened this issue Oct 6, 2012 · 0 comments
Closed

At start, ScoringService could score/token the same submission twice #31

lw opened this issue Oct 6, 2012 · 0 comments

Comments

@lw
Copy link
Member

lw commented Oct 6, 2012

This is what I got in the logs when I started SS on the day1 data of the IOI:

2012/10/06 18:07:12 - INFO     [ScoringService,0] Old submission yet to score/token: 785/3401.
2012/10/06 18:07:12 - INFO     [ScoringService,0] Old submission yet to score/token: 781/3401.
2012/10/06 18:07:13 - INFO     [ScoringService,0] Old submission yet to score/token: 777/3401.
2012/10/06 18:07:13 - INFO     [ScoringService,0] Old submission yet to score/token: 773/3401.
2012/10/06 18:07:18 - INFO     [ScoringService,0] Submissions found to score/token: 769, 3401.
2012/10/06 18:07:18 - INFO     [ScoringService,0] Old submission yet to score/token: 1538/6802.
2012/10/06 18:07:18 - INFO     [ScoringService,0] Old submission yet to score/token: 1534/6802.
2012/10/06 18:07:19 - INFO     [ScoringService,0] Old submission yet to score/token: 1530/6802.
2012/10/06 18:07:19 - INFO     [ScoringService,0] Old submission yet to score/token: 1526/6802.

It seems that SS at some point checked if there were submissions in the DB that weren't scored/tokened, found some (i.e. all those that were in the queue waiting to be scored/tokened) and put them in the queue, again!

Could someone (for example @stefano-maggiolo) check this?
waelsamy pushed a commit to waelsamy/cms that referenced this issue May 17, 2022
@fushar
Show confirmation dialog before reevaluation (cms-dev#31)
71eb38e
ranaldmiao pushed a commit to ranaldmiao/cms that referenced this issue Aug 10, 2022
@fushar
Show confirmation dialog before reevaluation (cms-dev#31)
089df47
pobrn pushed a commit to ioi-2023/cms that referenced this issue Feb 28, 2023
@fushar @pobrn
Show confirmation dialog before reevaluation (cms-dev#31)
d2eae7b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lw @stefano-maggiolo