Protect tracklet evaluation inputs from output collisions - #271
Draft
FlorianPfaff wants to merge 2 commits into
Draft
Protect tracklet evaluation inputs from output collisions#271FlorianPfaff wants to merge 2 commits into
FlorianPfaff wants to merge 2 commits into
Conversation
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Summary
Root cause
beltmap-evaluate-trackletsforwarded user-selected output paths directly togenerate_tracklet_evaluation_report(). The generator writes metrics JSON, then match CSV, then the Markdown report without checking whether those paths are distinct.Consequently, an output could overwrite the truth or prediction input after it had been loaded, or a later output could silently replace an earlier artifact while the command still returned success. Equivalent path spellings such as
reports/../truth.jsonwere also accepted.Impact
Destructive or ambiguous path layouts now fail through the CLI parser before any evaluation read/write workflow begins. Normal default and distinct explicit paths are unchanged.
Validation
main