This is an automated email from the ASF dual-hosted git repository.
jason810496 pushed a change to branch jason/lang-sdk-e2e/03-native-dag-parse
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit e5e417fbd53 Apply the team rules to the Dag that validation returns
omit 1c8d7863183 Test the import errors of a bundle with several
coordinators of a class
omit b8f8b5b16c0 Find a claiming Dag importer instead of its coordinator in
Dag processing
omit 24b328eb48a Name the coordinator class a native Dag task must be
routed to
omit b8ed37b1f2b Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
omit d71778333f3 Pass a parse log handle to the Lang-SDK processor in tests
omit dc169f9d9cf Find a native Dag's coordinator key through its importer
omit eefea5e14ac Wait for the killed leftover in the Lang-SDK processor test
omit bdcc2fd2ad4 Move the client-less Lang-SDK parse out of this change
omit 032c5ab5f99 Note in ADR-0010 that the manager routes claimed files for
now
omit a7834487346 Clear import errors after the native-file Dag bag sync test
omit 8fb2981a4a2 Apply the multi-team task checks to Lang-SDK Dags
omit 1b85bc0960e Spec the mocks of a hand-built Lang-SDK processor in tests
omit e2bf0eae0b9 Name the setting in a Lang-SDK parse timeout error
omit 4c55b0eb242 Kill what a Lang-SDK runtime leaves in its process group
omit 02514169e3d Match the schema error's JSON path in a Lang-SDK parse test
omit caf13de7d4e Fail a native Dag's task on a Python worker without retries
omit 3e770671eef Find the claiming coordinator in the Task SDK and wrap it
in core
omit 1178207f30b Start each Dag file processor with explicit arguments
omit f27abd6d039 Drop callbacks for Lang-SDK Dag files before queuing the
file
omit 4fce878ad09 Report a native Dag's task that reaches a Python worker
omit 5bd17e7f5bf Report a Lang-SDK parse past its import timeout as an
import error
omit 5a6e21b7028 Parse coordinator-claimed Dag files with their runtime in
the Dag processor
omit aef23367721 Describe how a Dag importer finds its coordinator in
ADR-0010
omit e004a3b2173 Let a Dag importer find the coordinator that parses its
files
add b9bdf5419aa Let a Dag importer find the coordinator that parses its
files
add 6fd170439a4 Describe how a Dag importer finds its coordinator in
ADR-0010
add ec74107656a Parse coordinator-claimed Dag files with their runtime in
the Dag processor
add a658e511c49 Report a Lang-SDK parse past its import timeout as an
import error
add db47446a6ed Report a native Dag's task that reaches a Python worker
add 96c32267afc Drop callbacks for Lang-SDK Dag files before queuing the
file
add 29ae6e2fa6e Start each Dag file processor with explicit arguments
add 1611330ed3e Find the claiming coordinator in the Task SDK and wrap it
in core
add 6735f2a433d Fail a native Dag's task on a Python worker without retries
add 6102868b7da Match the schema error's JSON path in a Lang-SDK parse test
add 1cbc4dfb9a7 Kill what a Lang-SDK runtime leaves in its process group
add b3a1b4b19bc Name the setting in a Lang-SDK parse timeout error
add a60ad59da7f Spec the mocks of a hand-built Lang-SDK processor in tests
add 4a4c5d426b8 Apply the multi-team task checks to Lang-SDK Dags
add 7e8364ff07b Clear import errors after the native-file Dag bag sync test
add 31c2b62bbbb Note in ADR-0010 that the manager routes claimed files for
now
add e9677cbf7b5 Move the client-less Lang-SDK parse out of this change
add 62fff240b11 Wait for the killed leftover in the Lang-SDK processor test
add 57d4c6111e1 Find a native Dag's coordinator key through its importer
add 3400a3027d8 Pass a parse log handle to the Lang-SDK processor in tests
add 7d894953d2e Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
add d8e8e35f4fe Name the coordinator class a native Dag task must be
routed to
add bf9c91a31c4 Find a claiming Dag importer instead of its coordinator in
Dag processing
add d050e698ccc Test the import errors of a bundle with several
coordinators of a class
add 79bef76bf7a Apply the team rules to the Dag that validation returns
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (e5e417fbd53)
\
N -- N -- N refs/heads/jason/lang-sdk-e2e/03-native-dag-parse
(79bef76bf7a)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
