Skip to content

Dn 327 + 333 + 334 + 335 #337

Merged
dnava23 merged 13 commits intomasterfrom
dn-327
Apr 11, 2025
Merged

Dn 327 + 333 + 334 + 335 #337
dnava23 merged 13 commits intomasterfrom
dn-327

Conversation

@dnava23
Copy link
Collaborator

@dnava23 dnava23 commented Apr 10, 2025

Description

Fixes #327

  • Changes the way standings are calculated
  • Standings are calculated every 5 minutes
  • Standings are fetched from the database if the 5 minutes have not passed yet

Fixes #333

  • Updated one of the caching dependencies that is used for the GitHub workflow tests

Fixes #334

  • On the submission page for judges, the score, testcases, and status are now updated visually without having the need to refresh the page

Fixes #335

  • On the home page for judges, a new table was added that displays the submissions that are next up in the queue to use Piston

Type of change

  • 🐞 Bug fix
  • 💡 New feature
  • ⚠️ Breaking change
  • 🧹 Code Cleanup
  • 📚 Documentation Change

How Has This Been Tested?

  • Tested individually.

Checklist:

  • My code follows the style guidelines of this project.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • My changes generate no new warnings.
  • My changes do not break any features.

…hey each get one data entry)

- Standings are now calculated every 15 minutes and the data entries are updated in the database
- If it is before the 15 minutes, the standings are grabbed from the database, which should help with load
- Still need to do general clean up on commented out code and make sure styling is consistent
…r judges

- Added "Submissions Next in Queue" table to the home page for judges to display which submissions from the doubly linked list are going to be sent to the queue
- Fixed issues where content on the submission page for judges would not visually update automatically unless the page was refreshed
- Added comments for files in the previous commit and for this commit
- Testing to see if Test Backend for Github workflow is successful
- Updated node-version in test-backend and test-frontend
@gitguardian
Copy link

gitguardian bot commented Apr 10, 2025

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
16267899 Triggered Generic Password 5f484b7 .docker/init-mongo.js View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@dnava23 dnava23 merged commit 5294074 into master Apr 11, 2025
4 checks passed
@dnava23 dnava23 deleted the dn-327 branch April 11, 2025 21:43
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.

Submissions Queue Updating Submissions View Backend Testing Rework Standings

3 participants