Repository navigation
Java SDK: Resolve a task's arguments from the Dag's own wiring - #73596
Merged
jason810496 merged 3 commits intoOct 2, 2026
Merged
Conversation
This was referenced Sep 23, 2026
jason810496
force-pushed
the
feature/java-sdk-wired-inputs
branch
6 times, most recently
from
September 27, 2026 14:48
77d08ec to
7a07fa3
Compare
1 task done
jason810496
force-pushed
the
feature/java-sdk-wired-inputs
branch
2 times, most recently
from
September 27, 2026 15:39
5d53589 to
da51a93
Compare
1 task done
jason810496
force-pushed
the
feature/java-sdk-wired-inputs
branch
3 times, most recently
from
September 30, 2026 08:40
0621b3d to
9a6166e
Compare
jason810496
marked this pull request as ready for review
September 30, 2026 09:01
guan404ming
reviewed
Sep 30, 2026
jason810496
marked this pull request as draft
October 1, 2026 06:55
jason810496
marked this pull request as ready for review
October 1, 2026 08:31
jason810496
commented
Oct 1, 2026
jason810496
left a comment
Member
Author
There was a problem hiding this comment.
Thanks for the review
FrankYang0529
approved these changes
Oct 2, 2026
A Dag authored in Java has no Python call site, so the supervisor sends no argument bindings for it and a task's data parameters had nothing to resolve against. Where the Dag wired inputs for a task, those stand in; a stub-backed task keeps reading its bindings, including when the call site bound none. The authoring surface that records those inputs lands in the next commit, so nothing declares them yet.
guan404ming
force-pushed
the
feature/java-sdk-wired-inputs
branch
from
October 2, 2026 07:50
24bffde to
04855b4
Compare
henry3260
approved these changes
Oct 2, 2026
uranusjr
approved these changes
Oct 2, 2026
uranusjr
left a comment
Member
There was a problem hiding this comment.
The one open nit should be addressed, otherwise lgtm.
pierrejeambrun
approved these changes
Oct 2, 2026
1 task done
1 task done
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
This PR add the argument binding for native Dag TaskFlow.
How
nullfor a boxed or reference parameter,MissingXComExceptionnaming the task for a primitive.This is the runtime half on its own. Nothing declares wired inputs until the next PR adds
@Builder.Deps.Was generative AI tooling used to co-author this PR?