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.

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

Migration Failures from DOMjudge 7.x to 8.x: Hash Inconsistencies and Missing Judgetasks #2509

Open
hqy2000 opened this issue Apr 24, 2024 · 0 comments

Comments

@hqy2000
Copy link

hqy2000 commented Apr 24, 2024

Description of the problem

The migration scripts from 7.x to 8.x fail to migrate certain data:

  1. They do not properly generate hash values for executables (see webapp/migrations/Version20210407120356.php), causing judgehosts to crash due to hash inconsistencies.
  2. They fail to generate judgetasks for existing judgeruns. Therefore, when modifying global/contest configurations, maybeCreateJudgeTasks crashes due to the creation of duplicate values.

Your environment

DOMjudge 8.2.2

Steps to reproduce

  1. Install DOMjudge 7.x.
  2. Create some submissions and judgeruns.
  3. Follow the Upgrading guide to upgrade to DOMjudge 8.x.
  4. Create additional submissions and modify configuration values.

Expected behaviour

Submissions should be correctly judged, and configuration values should be updated without issues.

Actual behaviour

Judgehosts crash. The DOMserver returns a 500 error due to foreign key violations.

Any other information that you want to share?

We have attempted some fixes in our fork: 30b2606 and bf66294. However, these fixes are specific to our cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants