#3292 sort input bound
Pull request opened by
pingsutw
## Tracking issue
NA
## Why are the changes needed?
Fails to register the map task with partial inputs because the _bound_inputs are not in order. If the order changes, Admin receives a different TaskTemplate and raises an error at registration time.
## What changes were proposed in this pull request?
sort _bound_inputs
## How was this patch tested?
import functools
from union import workflow, task, ImageSpec, map
image = ImageSpec(
builder="union",
packages=["union==0.1.182"],
)
@task(container_image=image)
def my_task(a: int, b: int, c: int, d: int, e: int) -> int:
print("adding one...")
return 2
@workflow
def wf():
vals = [1,2,3,4,5]
# t1 = functools.partial(my_task, b=1, c=1)
# _ = map(t1, bound_inputs={"b", "c"})(a=vals)
_ = map(my_task, bound_inputs={"b": 1, "c": 1, "d": 1, "e": 1})(a=vals)
### Setup process
### Screenshots
## Check all the applicable boxes
• I updated the documentation accordingly.
• All new and existing tests passed.
• All commits are signed-off.
## Related PRs
## Docs link
https://bito.ai#summarystart|
### Summary by Bito
This pull request improves the workflow model by sorting bound inputs, addressing issues with unsorted inputs that could cause registration errors for map tasks. This enhancement increases the reliability of task registration.
flyteorg/flytekit