This is an automated email from the ASF dual-hosted git repository.

jason810496 pushed a change to branch jason/lang-sdk-e2e/08-native-e2e
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 8895eb0020f Name the skipped-branch e2e test after what it checks
 discard 7d95ad86171 Document how the TypeScript example's native Dag gets 
parsed
 discard c46352b6df9 Explain why the k8s native TypeScript Dag test is skipped
 discard cb1e7d35689 Pack the TypeScript example against the built SDK
 discard c573022ed97 Build the TypeScript SDK before packing the k8s example 
bundle
 discard 4ca79ec2a76 Key the Lang-SDK e2e jobs on native Dag modules only
 discard feaa480434b Build the k8s TypeScript artifacts only for the native Dag 
test
 discard 42fe4c470ea Share the Dag run lookup and the native Java queue name
 discard 40d6fda5c5e Run the Lang-SDK e2e jobs when native Dag parsing changes
 discard aec31780076 Add a native Java Dag to the compose e2e
 discard e6427f513b3 Keep the containerized Java build's Maven repository on 
the host
 discard a06e48856ac Check the native TypeScript Dag's source and triggered run
 discard bddd682bd91 Parse the native TypeScript Dag in the compose e2e
 discard 60e855f9758 TS SDK: cover native TypeScript Dags end to end
 discard 51aab34160f Java SDK: Serialize native Dags to DagSerialization v3 on 
parse requests
 discard 9f54ff06de9 Java SDK: Declare a Dag's task graph with @Builder.Deps
 discard 23a6f677673 TS SDK: add triggerDagRun to the native Dag surface
 discard 5d99b09a78e TS SDK: add multi-way branching with dag.switch
 discard 4911badba47 TS SDK: add conditional branching with dag.if
 discard 7df8d1fc6fc Stub Dag file discovery with DagFileInfo in the Lang-SDK 
manager tests
 discard 5ae9612bf91 Handle Dags nested at any depth in Dag archives
 discard 13f4d4c345b Migrating from filepath based Dag to DagDefinition 
discovery
 discard 44f422dea17 Hand out the Node Dag importer through get_dag_importer
 discard 4e5d37bf8f3 Pin the Code view to the entry module in Node bundle tests
 discard 44bef1e3761 Let NodeDagImporter source read errors reach the caller
 discard 25b8a2d858c Import NodeDagImporter at the top of the Node coordinator
 discard fed3ceadbc4 Warn against defining a Dag in both TypeScript and Python
 discard 574c46a7ab8 Align the TypeScript build docs with the Code view
 discard 71f9d62ddfe Say when the Dag processor needs Node.js for TypeScript 
bundles
 discard 6a997106e79 Run a native TypeScript Dag's task from its own bundle
 discard 2c730e212f4 Share the bundle section mutation helper between Node tests
 discard 3d4f852aacf Document parsing native TypeScript Dags
 discard ed5bf214f23 Parse native TypeScript Dags with the Node coordinator
 discard b3a04e2a58e Hand out the Java Dag importer through get_dag_importer
 discard ecb55b91bcd Keep the Java parse_dag test from changing the pytest 
worker
 discard 204ddea7bd8 Stop promising that Java dependency JARs are not parsed
 discard bc7876e38f8 Reject a Java Dag JAR whose SDK cannot answer a parse
 discard 5f546e305c4 Run the JAR a native Java Dag was parsed from
 discard 62c038ff917 Report why a Java Dag JAR cannot be read
 discard 620f89fcecd Pass the task's Dag file to the coordinator's command 
builder
 discard f4596dd2243 Run a task on its run's version when dag_bundle_name names 
its bundle
 discard 1bd815e6de5 Document native Java Dag parsing
 discard f6fafbced57 Name the JAR manifest attributes the Java coordinator reads
 discard af129828a82 Test the Java Dag source placeholder for a JAR without a 
manifest
 discard 2662263ad46 Treat an unreadable JAR like one without a manifest
 discard ee7cdd6926a Parse native Java Dags with their coordinator
 discard bcd2defe70b Embed the Dag source in Java bundle JARs
 discard ba557380901 Build the JVM command that parses a Dag JAR
 discard b642ce42b7c Read JAR manifests per the JAR specification
 discard 9c3e5f0c0d5 Let a Dag file processor run without a parse log file
 discard 82f000bb947 Ignore the bagged Dag union in the external task sensor 
test
 discard 0b449b3d908 List the tasks of a native Lang-SDK Dag
 discard 69590246fdb Bag native Lang-SDK Dags in core, only when asked
     add fc9599900c5 Bag native Lang-SDK Dags in core, only when asked
     add 73f9d12a649 List the tasks of a native Lang-SDK Dag
     add a3bb832b891 Ignore the bagged Dag union in the external task sensor 
test
     add 964f50b5f99 Let a Dag file processor run without a parse log file
     add 78099b8d9be Read JAR manifests per the JAR specification
     add a72469e307f Build the JVM command that parses a Dag JAR
     add ebc635b170e Embed the Dag source in Java bundle JARs
     add fe152f658fd Parse native Java Dags with their coordinator
     add 9aac3dd1418 Treat an unreadable JAR like one without a manifest
     add a7548bf4b70 Test the Java Dag source placeholder for a JAR without a 
manifest
     add 59b02b9159e Name the JAR manifest attributes the Java coordinator reads
     add 7e88a2a1279 Document native Java Dag parsing
     add 5d9fa0b0c88 Run a task on its run's version when dag_bundle_name names 
its bundle
     add fc6aac9f25f Pass the task's Dag file to the coordinator's command 
builder
     add f4c25008c6f Report why a Java Dag JAR cannot be read
     add 8594141f4d6 Run the JAR a native Java Dag was parsed from
     add db32bd7d54a Reject a Java Dag JAR whose SDK cannot answer a parse
     add 77fef7215e8 Stop promising that Java dependency JARs are not parsed
     add 5a5d7e9606d Keep the Java parse_dag test from changing the pytest 
worker
     add 8a78c78fbf5 Hand out the Java Dag importer through get_dag_importer
     add b2981d2b2cc Parse native TypeScript Dags with the Node coordinator
     add f448056d507 Document parsing native TypeScript Dags
     add 9c7cc7280f3 Share the bundle section mutation helper between Node tests
     add f9d516bf9c3 Run a native TypeScript Dag's task from its own bundle
     add 2c0632ff9e5 Say when the Dag processor needs Node.js for TypeScript 
bundles
     add b0820932768 Align the TypeScript build docs with the Code view
     add 8c889eb1943 Warn against defining a Dag in both TypeScript and Python
     add eafca32ded1 Import NodeDagImporter at the top of the Node coordinator
     add 4011f4d4373 Let NodeDagImporter source read errors reach the caller
     add 3d8fcf9ecb8 Pin the Code view to the entry module in Node bundle tests
     add 878402f8657 Hand out the Node Dag importer through get_dag_importer
     add 09092f295c6 Migrating from filepath based Dag to DagDefinition 
discovery
     add df717afc70b Handle Dags nested at any depth in Dag archives
     add ae06452c18c Stub Dag file discovery with DagFileInfo in the Lang-SDK 
manager tests
     add 3eaf75557a4 TS SDK: add conditional branching with dag.if
     add 88249cfd9d2 TS SDK: add multi-way branching with dag.switch
     add 615f6ae5a81 TS SDK: add triggerDagRun to the native Dag surface
     add 5537e6e1d0f Java SDK: Declare a Dag's task graph with @Builder.Deps
     add 9e4826a8487 Java SDK: Serialize native Dags to DagSerialization v3 on 
parse requests
     add f41eee66271 TS SDK: cover native TypeScript Dags end to end
     add 2db6a5204c7 Parse the native TypeScript Dag in the compose e2e
     add d127443769a Check the native TypeScript Dag's source and triggered run
     add a4ad46a368e Keep the containerized Java build's Maven repository on 
the host
     add a8bc33e2ecf Add a native Java Dag to the compose e2e
     add baa0a7a500f Run the Lang-SDK e2e jobs when native Dag parsing changes
     add df41931a991 Share the Dag run lookup and the native Java queue name
     add 05939bd86fe Build the k8s TypeScript artifacts only for the native Dag 
test
     add 29e8e523450 Key the Lang-SDK e2e jobs on native Dag modules only
     add 7662704170e Build the TypeScript SDK before packing the k8s example 
bundle
     add 932e21968ec Pack the TypeScript example against the built SDK
     add eb68e7ebe3b Explain why the k8s native TypeScript Dag test is skipped
     add bab306bbf8c Document how the TypeScript example's native Dag gets 
parsed
     add 731af2ec5ef Name the skipped-branch e2e test after what it checks

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   (8895eb0020f)
            \
             N -- N -- N   refs/heads/jason/lang-sdk-e2e/08-native-e2e 
(731af2ec5ef)

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:
 airflow-core/src/airflow/dag_processing/dagbag.py     | 11 +++++++----
 airflow-core/src/airflow/dag_processing/processor.py  |  5 ++---
 airflow-core/src/airflow/utils/cli.py                 |  7 +++----
 airflow-core/tests/unit/dag_processing/test_dagbag.py | 12 ++++++++++++
 4 files changed, 24 insertions(+), 11 deletions(-)

Reply via email to