Skip to content

[Bugfix:TAGrading] Fix Peer Component Version Conflict#13000

Merged
bmcutler merged 1 commit into
mainfrom
fix-peer-version-conflict
Jul 5, 2026
Merged

[Bugfix:TAGrading] Fix Peer Component Version Conflict#13000
bmcutler merged 1 commit into
mainfrom
fix-peer-version-conflict

Conversation

@mattLif

@mattLif mattLif commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Why is this Change Important & Necessary?

Fixes #10772
Since the process of determining graded version did not include the tag used for peer components (just regular components), NaN was being registered as the graded version for peer components. This caused unnecessary version conflict messages.

What is the New Behavior?

Before:
image

After:
image

What steps should a reviewer take to reproduce or test the bug or new feature?

On Main:

  1. Go to grading a gradeable with peer components
  2. Open the grading rubric for a student that has been graded
  3. Open and close a component several times.
  4. See Version Conflict NaN

On Branch:

  1. Repeat steps 1-3 like on main
  2. Verify no version conflict appears

Automated Testing & Documentation

No automated testing added nor documentation needed.

Other information

Not a breaking change
No migrations
Not a security concern

@codecov

codecov Bot commented Jul 3, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 21.41%. Comparing base (c33d434) to head (3d1078f).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff              @@
##               main   #13000      +/-   ##
============================================
- Coverage     21.41%   21.41%   -0.01%     
  Complexity    10002    10002              
============================================
  Files           277      277              
  Lines         37418    37419       +1     
  Branches        512      513       +1     
============================================
  Hits           8013     8013              
  Misses        28904    28904              
- Partials        501      502       +1     
Flag Coverage Δ
autograder 21.16% <ø> (ø)
js 1.98% <0.00%> (-0.01%) ⬇️
migrator 100.00% <ø> (ø)
php 20.37% <ø> (ø)
python_submitty_utils 80.08% <ø> (ø)
submitty_daemon_jobs 91.13% <ø> (ø)
vue 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mattLif mattLif changed the title [Bugfix:TAGrading] Fix Peer Component Version Conflix [Bugfix:TAGrading] Fix Peer Component Version Conflict Jul 3, 2026

@dagemcn dagemcn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was able to observe the incorrect behavior on main, after checking out the branch and testing I was able to confirm that the error no longer appears. Looks good!

@github-project-automation github-project-automation Bot moved this from Seeking Reviewer to Awaiting Maintainer Review in Submitty Development Jul 3, 2026
@bmcutler
bmcutler merged commit c00f01b into main Jul 5, 2026
32 checks passed
@bmcutler
bmcutler deleted the fix-peer-version-conflict branch July 5, 2026 12:50
@github-project-automation github-project-automation Bot moved this from Awaiting Maintainer Review to Done in Submitty Development Jul 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Peer Grading displays unnecessary Version Conflict

3 participants