This is an automated email from the ASF dual-hosted git repository.
jason810496 pushed a change to branch jason/java-sdk/native-dag-trigger-dag-run
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 93f3da61146 Java SDK: Check a trigger task polls the run it started
omit 08d95210156 Java SDK: Run a trigger task through runTask in tests
omit 7ce837a8fd3 Java SDK: Leave the trigger fixture's logical date to the
Go SDK change
add e638c382553 Java SDK: Give the trigger fixture a logical date every
SDK can write
add 192db48d10c Java SDK: Run a trigger task through runTask in tests
add c4a82f66f43 Java SDK: Check a trigger task polls the run it started
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 (93f3da61146)
\
N -- N -- N refs/heads/jason/java-sdk/native-dag-trigger-dag-run
(c4a82f66f43)
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:
.../kotlin/org/apache/airflow/sdk/conformance/SerializeJava.kt | 8 +++++++-
scripts/ci/lang_sdk_serialization/test_dags.yaml | 5 ++++-
2 files changed, 11 insertions(+), 2 deletions(-)
