Uh oh!
There was an error while loading. Please reload this page.
Fix patch_task_instance endpoint - #50550
Conversation
5c447cf to
39cd8c7Compare
jason810496
left a comment
There was a problem hiding this comment.
Thanks!
Follow up:
I think we can extract the map_index query parameter into a common parameter class to handle the logic:map_index = -1 if map_index is None else map_index directly in the router.
I'll raise a follow-up PR after this one is merged.
pierrejeambrun
commented
May 14, 2025
This was just to limit the PR to the change spec, but with #50526 this lines won't exist anymore. (None will be handled as summary) |
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker db89cc0 v3-0-testThis should apply the commit to the v3-0-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
(cherry picked from commit db89cc0)
(cherry picked from commit db89cc0)
Update spec for the
patch_task_instance_endpoint. This is necessary to be able to handle in the future task instance summaries (all the map_indexes for a given TI) and task groups.This fell through the cracks and need to be fixed.