fix(core): register task timings correctly in task profiling life cycle #16801
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.
Current Behavior
In the
TaskProfilingLifeCycle
class the task timings are registered with a manually crafted key instead of using the task id. When processing the task results, timings are set with the task id which throws because of the mismatch.Expected Behavior
In the
TaskProfilingLifeCycle
class the task timings should be registered with the task id.Related Issue(s)
Fixes #16792