Skip to content

Handle direct mapping states in MTT mean extraction - #5242

Open
FlorianPfaff wants to merge 2 commits into
mainfrom
agent/fix-direct-mtt-mapping-state
Open

Handle direct mapping states in MTT mean extraction#5242
FlorianPfaff wants to merge 2 commits into
mainfrom
agent/fix-direct-mtt-mapping-state

Conversation

@FlorianPfaff

Copy link
Copy Markdown
Owner

Bug

get_extract_mean("euclidean", mtt_scenario=True) already extracts mapping values when a tracker exposes them through .tracks or get_tracks(). However, passing the equivalent mapping directly as the filter state falls through to _point_estimate_or_mean(...), so the dictionary itself is returned instead of the per-track estimates.

This makes semantically equivalent MTT state representations behave differently and can leak track objects into evaluation output.

Fix

Treat a direct Mapping like the already-supported list and tuple track collections. The existing _extract_track_collection_mean(...) helper then preserves mapping insertion order and extracts each track's point estimate or mean.

Regression coverage

Add a focused test for a plain {track_id: track} state and verify that it returns an ordered list of numeric track means.

Validation

  • reproduced the failure against current main (1 failed, 2 passed);
  • applied the one-line dispatch fix;
  • focused regression suite passes (3 passed);
  • both changed files compile successfully;
  • branch is 2 commits ahead and 0 behind main, with only 17 changed lines across the implementation and test.

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

MegaLinter analysis: Success

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ COPYPASTE jscpd yes no no 29.33s
✅ JSON prettier 7 0 0 0 1.71s
✅ JSON v8r 7 0 0 5.28s
✅ MARKDOWN markdownlint 68 0 0 0 1.98s
✅ MARKDOWN markdown-table-formatter 68 0 0 0 0.67s
✅ PYTHON black 1865 87 0 0 102.32s
✅ PYTHON isort 1865 139 0 0 2.95s
✅ REPOSITORY betterleaks yes no no 2.57s
✅ REPOSITORY checkov yes no no 56.91s
✅ REPOSITORY gitleaks yes no no 18.69s
✅ REPOSITORY git_diff yes no no 0.55s
✅ REPOSITORY secretlint yes no no 89.03s
✅ REPOSITORY syft yes no no 5.34s
✅ REPOSITORY trivy-sbom yes no no 6.24s
✅ REPOSITORY trufflehog yes no no 33.62s
✅ YAML prettier 11 0 0 0 0.92s
✅ YAML v8r 11 0 0 13.61s
✅ YAML yamllint 11 0 0 0.61s

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters PYTHON_BLACK,PYTHON_ISORT,COPYPASTE_JSCPD,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_BETTERLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@FlorianPfaff
FlorianPfaff marked this pull request as ready for review August 7, 2026 17:58
@FlorianPfaff
FlorianPfaff enabled auto-merge (squash) August 7, 2026 17:58
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.

1 participant