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

Add option to specify an additional overshoot time when kicking off a… #2735

Merged
merged 1 commit into from
Oct 6, 2024

Conversation

meisterT
Copy link
Member

@meisterT meisterT commented Oct 5, 2024

… rejudging.

Fixes #2700.

@vmcj
Copy link
Member

vmcj commented Oct 5, 2024

PHPStan found some issues.

@meisterT
Copy link
Member Author

meisterT commented Oct 5, 2024

Phpstan is happy now

@meisterT meisterT added this pull request to the merge queue Oct 6, 2024
Merged via the queue into DOMjudge:main with commit 652bb06 Oct 6, 2024
26 checks passed
@meisterT meisterT deleted the rejudgeovershoot branch October 6, 2024 11:15
Copy link

sentry-io bot commented Oct 7, 2024

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

  • ‼️ Doctrine\DBAL\Exception\UniqueConstraintViolationException: An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1... /src/Service/DOMJudgeService.php in App\Service... View Issue
  • ‼️ Doctrine\DBAL\Exception\UniqueConstraintViolationException: An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1... /src/Service/DOMJudgeService.php in App\Service... View Issue

Did you find this useful? React with a 👍 or 👎

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

Successfully merging this pull request may close these issues.

Allow to specify a higher overshoot value in a rejudging
2 participants