This is an automated email from the ASF dual-hosted git repository.
jason810496 pushed a change to branch
jason/lang-sdk-e2e/01-coordinator-dag-bundle-name
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard b238a022c47 Reject blank subprocess coordinator artifact roots
discard 6dc4ee7384a Reject empty subprocess coordinator artifact roots
discard f79d7502c2c Reject concurrent subprocess coordinator execution
consistently
discard 5e210e8f8d6 Make task bundle access dependencies explicit
discard 13b4a38ac26 Preserve custom subprocess coordinator compatibility
discard ac1f620daec Read the Dag bundle configuration through a single entry
point
discard 6523b0581c3 Resolve coordinator Dag bundles without importing the task
runner
discard aa32014083c Make JavaCoordinator main_class optional in co-located mode
discard fec090c4e62 Harden subprocess coordinator artifact bundle resolution
discard 1a65f90325e Document dag_bundle_name option for language-SDK
coordinators
discard 86d5297ca4b Add dag_bundle_name option to subprocess coordinators
add 84f75158120 Require `common.sql` 2.2.0 for common.ai's SQL extras
(#73867)
add d8c78379e77 Add dag_bundle_name option to subprocess coordinators
add 9257c50cf16 Document dag_bundle_name option for language-SDK
coordinators
add 0e857247f41 Harden subprocess coordinator artifact bundle resolution
add e6c1deca9d9 Make JavaCoordinator main_class optional in co-located mode
add 8c674c638d5 Resolve coordinator Dag bundles without importing the task
runner
add e9da1565f5b Read the Dag bundle configuration through a single entry
point
add 68cca25a3e1 Preserve custom subprocess coordinator compatibility
add a6557be73bd Make task bundle access dependencies explicit
add bada0a79306 Reject concurrent subprocess coordinator execution
consistently
add e8e1a8ba506 Reject empty subprocess coordinator artifact roots
add 18334707dec Reject blank subprocess coordinator artifact roots
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 (b238a022c47)
\
N -- N -- N
refs/heads/jason/lang-sdk-e2e/01-coordinator-dag-bundle-name (18334707dec)
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:
providers/common/ai/README.rst | 4 +--
providers/common/ai/docs/index.rst | 4 +--
providers/common/ai/docs/retry_policies.rst | 39 +++++++++++-----------
providers/common/ai/pyproject.toml | 4 +--
.../ai/example_dags/example_classifier_model.py | 8 +++--
5 files changed, 30 insertions(+), 29 deletions(-)
