[BUG] v2 PredictCallback.return_info misreads batched y and index metadata - #2401
[BUG] v2 PredictCallback.return_info misreads batched y and index metadata#2401victorwon2001 wants to merge 2 commits into
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2401 +/- ##
=======================================
Coverage ? 88.06%
=======================================
Files ? 200
Lines ? 11242
Branches ? 0
=======================================
Hits ? 9900
Misses ? 1342
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Updated both v2 tutorial prediction examples to read the returned index as a DataFrame row and display |
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
LLM generated content, by GPT-5.6 Sol
Reference Issues/PRs
Fixes #2156
What does this implement/fix? Explain your changes.
Corrects v2 prediction metadata so
return_inforeturns the full target batch, a prediction index derived from the active dataset, and consistent prediction lengths across the supported data modules.What should a reviewer concentrate their feedback on?
Whether the returned index matches the intended v2 prediction contract.
Did you add any tests for the change?
Yes. Focused regression tests cover batched and multi-target targets, prediction indices, and both v2 data paths. The affected suites and pre-commit checks pass.
Any other comments?
None.
PR checklist