[Bugfix:Autograding] Multiple docker debugging errors

[Chriun]

Please check if the PR fulfills these requirements:

• Tests for the changes have been added/updated (if possible)
• Documentation has been updated/added if relevant
• Screenshots are attached to Github PR if visual/UI changes were made

What is the current behavior?

Fixes #11645
Currently, if there is a required docker image for an gradeable is missing, autograding submissions notify both students and instructors in the autograding results box. However, if multiple images are required and are missing, the subsequent errors overwrite the details of the previous error.

What is the new behavior?

The subsequent errors are appended to a list of errors and looped through to display each image error.

Other information?

Current behavior

New behavior

[codecov]

Codecov Report

Attention: Patch coverage is 5.26316% with 18 lines in your changes missing coverage. Please review.

Project coverage is 22.48%. Comparing base (09fddcb) to head (9c9f63f).
Report is 12 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #11697      +/-   ##
============================================
- Coverage     22.48%   22.48%   -0.01%     
  Complexity     9080     9080              
============================================
  Files           252      252              
  Lines         32612    32623      +11     
  Branches         83       83              
============================================
+ Hits           7333     7334       +1     
- Misses        25200    25210      +10     
  Partials         79       79              

Flag	Coverage Δ
autograder	21.44% <5.26%> (-0.08%)	⬇️
js	27.17% <ø> (ø)
migrator	100.00% <ø> (ø)
php	19.57% <ø> (ø)
python_submitty_utils	80.08% <ø> (ø)
submitty_daemon_jobs	88.88% <ø> (ø)

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.

[JManion32]

I was able to replicate the issue and found that it is now resolved:

I do want to note that I encountered this frog robot a few times while testing, however, I think this is just because of the way I was setting it up as well as how I was testing a similar PR today.

[Chriun]

I was able to replicate the issue and found that it is now resolved:

I do want to note that I encountered this frog robot a few times while testing, however, I think this is just because of the way I was setting it up as well as how I was testing a similar PR today.

Yes I was running into the same error because the previous docker error was stored in a single dictionary and persisted in that gradeable's autograding results box. The new behavior expects a list of error dictionaries so entering a gradeable with the lingering error in the old format will give an attribute error. This should work properly outside of that and would never occur normally (outside our development environment).