This is an automated email from the ASF dual-hosted git repository.
ephraimbuddy pushed a change to branch dag-processor-work-delivery
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 8f1c3bf17e3 Retain Dag processor work until delivery is acknowledged
discard 5f00fff559b Align API-mode Dag publication with DB-mode cleanup
discard e2870d20133 Allow Dag processors to publish metadata through the
Execution API
add 445893dad7b Make the bundle refresh regression test independent of
uptime
add 45468cacf4b Allow Dag processors to publish metadata through the
Execution API
add 62cd45990b6 Align API-mode Dag publication with DB-mode cleanup
add bf8149e842c Retain Dag processor work until delivery is acknowledged
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 (8f1c3bf17e3)
\
N -- N -- N refs/heads/dag-processor-work-delivery (bf8149e842c)
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/tests/unit/dag_processing/test_manager.py | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)