[hotfix] Use correct files list for sorting annotations when viewing an archive #1616
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use result from
Archive.get_files
, rather than@files
, when callingget_correct_filename
inview
.Hotfix for #1590
Motivation and Context
Currently, we are using
@files
when finding the filenames for annotations.The problem with this is that
@files
is the result ofArchive.get_file_hierarchy
, whose length does not correspond directly to the number of files (subfiles are recursively nested). Rather its length is the number of "top level" files / directories.This further results in an error when
get_correct_filename
callsArchive.get_nth_filename
, potentially on an out of bounds index.However,
viewFeedback
handles this correctly since@files
is only set for Archives, and is set to the result ofArchive.get_files
.How Has This Been Tested?
Before
After
Types of changes
Checklist:
overcommit --install && overcommit --sign
to use pre-commit hook for linting