This is an automated email from the ASF dual-hosted git repository.
jason810496 pushed a change to branch jason/lang-sdk-e2e/03e-lang-sdk-dag-bag
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 29de12f6fc5 Default a Dag file processor's parse log to os.devnull
omit 926d36dbc8c Let a Dag file processor run without a parse log file
omit ea855e04b42 Ignore the bagged Dag union in the external task sensor
test
omit 914bc6dd1e6 List the tasks of a native Lang-SDK Dag
omit 55740382162 Bag native Lang-SDK Dags in core, only when asked
omit 1a017d1fe62 Let a Dag file processor run without an API client
omit 98288bf696c Parse coordinator-claimed Dag files with their runtime in
a Dag bag
omit e9b28933f3f Apply the team rules to the Dag that validation returns
omit f3114556f4b Test the import errors of a bundle with several
coordinators of a class
omit 696f7aaef03 Find a claiming Dag importer instead of its coordinator in
Dag processing
omit 2c260883398 Name the coordinator class a native Dag task must be
routed to
omit 6f1246adc45 Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
omit c6a79932394 Pass a parse log handle to the Lang-SDK processor in tests
omit fab8b8fb084 Find a native Dag's coordinator key through its importer
omit 1b8cc7c615b Wait for the killed leftover in the Lang-SDK processor test
omit ccaee070e64 Move the client-less Lang-SDK parse out of this change
omit 0aeaf24fc03 Note in ADR-0010 that the manager routes claimed files for
now
omit fa9d50f6484 Clear import errors after the native-file Dag bag sync test
omit 8b0574fc678 Apply the multi-team task checks to Lang-SDK Dags
omit 41af74c7be4 Spec the mocks of a hand-built Lang-SDK processor in tests
omit fb033be47ff Name the setting in a Lang-SDK parse timeout error
omit 4b34b45fc40 Kill what a Lang-SDK runtime leaves in its process group
omit 711162c0aa8 Match the schema error's JSON path in a Lang-SDK parse test
omit 8174afac07c Fail a native Dag's task on a Python worker without retries
omit 3b340d6c82a Find the claiming coordinator in the Task SDK and wrap it
in core
omit f536faef515 Start each Dag file processor with explicit arguments
omit bda4e74cd73 Drop callbacks for Lang-SDK Dag files before queuing the
file
omit 8b9abbac1a7 Report a native Dag's task that reaches a Python worker
omit a28778cd7f2 Report a Lang-SDK parse past its import timeout as an
import error
omit ec5f8dfc077 Parse coordinator-claimed Dag files with their runtime in
the Dag processor
omit 3dfc4d471ab Break the new dag_bundle_name docs only at sentence ends
omit f4fcbf2b6f0 Say which failures fall back to a Python file in ADR-0010
omit 5dd8b0a6392 Add a newsfragment for the removed coordinator artifact
roots
omit a123aea9f61 Describe how a Dag importer finds its coordinator in
ADR-0010
omit 0d425b4c442 Say dag_bundle_name only names the stub task artifact
bundle
omit 724ed151e0c Find a Dag importer's coordinator from its class
omit d32ba4d51fd Explain dag_bundle_name by the coordinator that parses a
Dag file
omit 62cd77cdb5c Hand out a coordinator's Dag importer through
get_dag_importer alone
omit 59252221619 Say dag_bundle_name is only needed for two coordinators of
one class
omit b1bc98b2ad3 Drop serves_bundle so get_parsed_bundles is the only answer
omit 95195316931 Check Dag file claims per bundle on the parse path
omit 1210fcd1a4f Import the coordinator manager at the top of the importer
base
omit f3e86043885 Let a coordinator parse the Dag files of the bundles it
serves
omit a729bf8866d Report a schema error's path the same way under every
jsonschema version
omit 962acf2c16b Check a serialized Dag as the SDK Dag is checked and
return it
omit c3113a96e4f Sync the Go SDK copy of the Dag schema
omit 340063d8a97 Sync the Java SDK copy of the Dag schema
omit 8659361cd63 Serialize the SDK Dag in tests that write a dag_maker Dag
omit 6866e98d3b0 Note in the parsing ADR that runtimes may omit
config-backed fields
omit b44ff24cdb1 Check SDK Dags with the Dag processor's validation in
conformance
omit 9ee09fe33c2 Reject malformed task entries in a serialized Dag
omit 5bd6db26da1 Fill a serialized Dag's unset settings from the Airflow
config
add 9ef13d3ca8c Fill a serialized Dag's unset settings from the Airflow
config
add 8636b093e38 Reject malformed task entries in a serialized Dag
add 6158ada8ab3 Check SDK Dags with the Dag processor's validation in
conformance
add 973cf03f119 Note in the parsing ADR that runtimes may omit
config-backed fields
add ac2244adbfb Serialize the SDK Dag in tests that write a dag_maker Dag
add e840e922684 Sync the Java SDK copy of the Dag schema
add e2b4e2972c7 Sync the Go SDK copy of the Dag schema
add 2bcf0508832 Check a serialized Dag as the SDK Dag is checked and
return it
add a7efc7c851c Report a schema error's path the same way under every
jsonschema version
add 82fa8626f8d Let a coordinator parse the Dag files of the bundles it
serves
add 90e3aad2a39 Import the coordinator manager at the top of the importer
base
add 68a619133ec Check Dag file claims per bundle on the parse path
add d38901621ad Drop serves_bundle so get_parsed_bundles is the only answer
add ce8aac3144b Say dag_bundle_name is only needed for two coordinators of
one class
add 95a9ed9f3d1 Hand out a coordinator's Dag importer through
get_dag_importer alone
add 0022eedf09d Explain dag_bundle_name by the coordinator that parses a
Dag file
add 58aade928ed Find a Dag importer's coordinator from its class
add fb6c4bfa6a8 Say dag_bundle_name only names the stub task artifact
bundle
add 8364bb2737d Describe how a Dag importer finds its coordinator in
ADR-0010
add eafec25b77c Add a newsfragment for the removed coordinator artifact
roots
add 122154d8737 Say which failures fall back to a Python file in ADR-0010
add 1e177e60233 Break the new dag_bundle_name docs only at sentence ends
add fe6a6853722 Parse coordinator-claimed Dag files with their runtime in
the Dag processor
add a359ae7da5d Report a Lang-SDK parse past its import timeout as an
import error
add faa3e2857c2 Report a native Dag's task that reaches a Python worker
add eb3982e6a70 Drop callbacks for Lang-SDK Dag files before queuing the
file
add 87ad555f970 Start each Dag file processor with explicit arguments
add 0e1b2cadf6f Find the claiming coordinator in the Task SDK and wrap it
in core
add c879d3f1a69 Fail a native Dag's task on a Python worker without retries
add 2da7ac9fe97 Match the schema error's JSON path in a Lang-SDK parse test
add 8b7641f14c2 Kill what a Lang-SDK runtime leaves in its process group
add f442ee85584 Name the setting in a Lang-SDK parse timeout error
add eabe577bd7d Spec the mocks of a hand-built Lang-SDK processor in tests
add 6cb611d6be3 Apply the multi-team task checks to Lang-SDK Dags
add ae441ffba17 Clear import errors after the native-file Dag bag sync test
add 303d6255397 Note in ADR-0010 that the manager routes claimed files for
now
add 359f8449cb4 Move the client-less Lang-SDK parse out of this change
add aee15031875 Wait for the killed leftover in the Lang-SDK processor test
add 49e05dd9988 Find a native Dag's coordinator key through its importer
add 0e176450f11 Pass a parse log handle to the Lang-SDK processor in tests
add ac5378598a7 Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
add 7aef9c68bca Name the coordinator class a native Dag task must be
routed to
add 84da01d4cd7 Find a claiming Dag importer instead of its coordinator in
Dag processing
add 17ed2288524 Test the import errors of a bundle with several
coordinators of a class
add edca3246501 Apply the team rules to the Dag that validation returns
add 05fc6dae5e9 Parse coordinator-claimed Dag files with their runtime in
a Dag bag
add 89396f186ea Let a Dag file processor run without an API client
add 2e8d1f2a676 Bag native Lang-SDK Dags in core, only when asked
add d90c9e30918 List the tasks of a native Lang-SDK Dag
add 87f4d3541c9 Ignore the bagged Dag union in the external task sensor
test
add 02da4901465 Let a Dag file processor run without a parse log file
add 1724f567cc6 Default a Dag file processor's parse log to os.devnull
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 (29de12f6fc5)
\
N -- N -- N refs/heads/jason/lang-sdk-e2e/03e-lang-sdk-dag-bag
(1724f567cc6)
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:
