This is an automated email from the ASF dual-hosted git repository.
jason810496 pushed a change to branch jason/lang-sdk-e2e/02-importer-registry
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit ae06452c18c Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
omit df717afc70b Handle Dags nested at any depth in Dag archives
omit 09092f295c6 Migrating from filepath based Dag to DagDefinition
discovery
omit 878402f8657 Hand out the Node Dag importer through get_dag_importer
omit 3d8fcf9ecb8 Pin the Code view to the entry module in Node bundle tests
omit 4011f4d4373 Let NodeDagImporter source read errors reach the caller
omit eafca32ded1 Import NodeDagImporter at the top of the Node coordinator
omit 8c889eb1943 Warn against defining a Dag in both TypeScript and Python
omit b0820932768 Align the TypeScript build docs with the Code view
omit 2c0632ff9e5 Say when the Dag processor needs Node.js for TypeScript
bundles
omit f9d516bf9c3 Run a native TypeScript Dag's task from its own bundle
omit 9c7cc7280f3 Share the bundle section mutation helper between Node tests
omit f448056d507 Document parsing native TypeScript Dags
omit b2981d2b2cc Parse native TypeScript Dags with the Node coordinator
omit 8a78c78fbf5 Hand out the Java Dag importer through get_dag_importer
omit 5a5d7e9606d Keep the Java parse_dag test from changing the pytest
worker
omit 77fef7215e8 Stop promising that Java dependency JARs are not parsed
omit db32bd7d54a Reject a Java Dag JAR whose SDK cannot answer a parse
omit 8594141f4d6 Run the JAR a native Java Dag was parsed from
omit f4c25008c6f Report why a Java Dag JAR cannot be read
omit fc6aac9f25f Pass the task's Dag file to the coordinator's command
builder
omit 5d9fa0b0c88 Run a task on its run's version when dag_bundle_name names
its bundle
omit 7e88a2a1279 Document native Java Dag parsing
omit 59b02b9159e Name the JAR manifest attributes the Java coordinator reads
omit a7548bf4b70 Test the Java Dag source placeholder for a JAR without a
manifest
omit 9aac3dd1418 Treat an unreadable JAR like one without a manifest
omit fe152f658fd Parse native Java Dags with their coordinator
omit ebc635b170e Embed the Dag source in Java bundle JARs
add e2821c281e2 Parse native Java Dags with their coordinator
add 2c97b771a29 Treat an unreadable JAR like one without a manifest
add 268bb0f300e Test the Java Dag source placeholder for a JAR without a
manifest
add 8aadc5dc059 Name the JAR manifest attributes the Java coordinator reads
add 606f57b5eb4 Document native Java Dag parsing
add 72c27be559e Run a task on its run's version when dag_bundle_name names
its bundle
add 04079e6b472 Pass the task's Dag file to the coordinator's command
builder
add 296625064c6 Report why a Java Dag JAR cannot be read
add 3789dca6483 Run the JAR a native Java Dag was parsed from
add e8ed427d8e0 Reject a Java Dag JAR whose SDK cannot answer a parse
add 44df95f0f29 Stop promising that Java dependency JARs are not parsed
add f04c85ec677 Keep the Java parse_dag test from changing the pytest
worker
add 1a83691279b Hand out the Java Dag importer through get_dag_importer
add ffa20db10b2 Read Java Dag sources from the bundle's sources.json index
add e4d42721628 Parse native TypeScript Dags with the Node coordinator
add 6cb30660a5c Document parsing native TypeScript Dags
add 74de1024b9b Share the bundle section mutation helper between Node tests
add 55187c1eed0 Run a native TypeScript Dag's task from its own bundle
add 5ab90091a46 Say when the Dag processor needs Node.js for TypeScript
bundles
add 97b8d05b9b3 Align the TypeScript build docs with the Code view
add 4fead1b372c Warn against defining a Dag in both TypeScript and Python
add 64743c38768 Import NodeDagImporter at the top of the Node coordinator
add 17714c8d2a8 Let NodeDagImporter source read errors reach the caller
add f4e0fb92c39 Pin the Code view to the entry module in Node bundle tests
add 6167d99ee05 Hand out the Node Dag importer through get_dag_importer
add 25da3489de0 Migrating from filepath based Dag to DagDefinition
discovery
add cc3bd5c4164 Handle Dags nested at any depth in Dag archives
add 82232048474 Stub Dag file discovery with DagFileInfo in the Lang-SDK
manager tests
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 (ae06452c18c)
\
N -- N -- N refs/heads/jason/lang-sdk-e2e/02-importer-registry
(82232048474)
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:
.../language-sdks/java.rst | 31 ++++----
.../apache/airflow/sdk/plugin/AirflowSdkPlugin.kt | 58 ---------------
.../airflow/sdk/coordinators/java/_dag_importer.py | 51 ++++++++++---
.../airflow/sdk/coordinators/java/_jar_manifest.py | 2 +-
.../coordinators/java/test_dag_importer.py | 87 ++++++++++++++++------
.../coordinators/java/test_jar_manifest.py | 6 +-
6 files changed, 122 insertions(+), 113 deletions(-)
