This is an automated email from the ASF dual-hosted git repository.
weilee pushed a change to branch render-json-logs-new-ui
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit a41661192ad feat(providers/elasticsearch): add airflow 3 task handler
log handling logic
add bd0c24728b0 feat(providers/elasticsearch): add airflow 3 task handler
log handling logic
add 075d8446cfd feat(providers/microsoft): add airflow 3 task handler log
handling logic
add 1e12987e851 feat(providers/redis): add airflow 3 task handler log
handling logic
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 (a41661192ad)
\
N -- N -- N refs/heads/render-json-logs-new-ui (1e12987e851)
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/elasticsearch/log/es_task_handler.py | 81 +++++-----------------
.../microsoft/azure/log/wasb_task_handler.py | 9 ++-
.../providers/microsoft/azure}/version_compat.py | 0
.../microsoft/azure/log/test_wasb_task_handler.py | 36 +++++++---
.../providers/redis/log/redis_task_handler.py | 4 ++
.../src/airflow/providers/redis}/version_compat.py | 0
.../unit/redis/log/test_redis_task_handler.py | 12 +++-
7 files changed, 68 insertions(+), 74 deletions(-)
copy providers/{amazon/src/airflow/providers/amazon =>
microsoft/azure/src/airflow/providers/microsoft/azure}/version_compat.py (100%)
copy providers/{amazon/src/airflow/providers/amazon =>
redis/src/airflow/providers/redis}/version_compat.py (100%)
