Fix misleading extrapolation time in buffer_core (#832)#896
Conversation
|
IMHO TF2 error detection logic should be more path-aware in general, but I just wanted to focus on this specific bug for now. |
tfoote
left a comment
There was a problem hiding this comment.
Thanks for adding this extra logic. Can you use the issue example to add a test case so that we can validate the error exists and that this fixes it and make sure that this doesn't regress at some point in the future.
The reproduction in the issues should provide most of what you need.
|
Done |
tfoote
left a comment
There was a problem hiding this comment.
Thanks for the test too. It looks good to me now.
|
Pulls: #896 |
|
https://github.com/Mergifyio backport kilted jazzy humble |
✅ Backports have been createdDetails
|
Description
This PR fixes the issue where extrapolation errors incorrectly prioritize metadata gathered during the initial source-to-root traversal (Phase 1). By comparing timestamps from both traversal phases, the error now correctly reports the 'latest data' time for the specific link on the requested transform path.
Verification
Reproduced with the script in #832:
Fixes #832