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 b609dc3d90a feat(api_connexion/log): update v1 api to the latest log
format
omit 9b94e31e994 test(api_fastapi): fix existing test_log unit tests
omit 6579cd7ac30 test(www): fix existing unit tests
omit 2a2dd0ef7a0 test(test_log_reader): fix existing unit tests
omit 96d64b6bda3 style: improve type annotation
add 7f25fffde7d style: improve type annotation
add 0b3b47a6e7c test(test_log_reader): fix existing unit tests
add f72516d946b test(www): fix existing unit tests
add ac28feb9411 test(api_fastapi): fix existing test_log unit tests
add 0e1855b5452 feat(api_connexion/log): update v1 api to the latest log
format
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 (b609dc3d90a)
\
N -- N -- N refs/heads/render-json-logs-new-ui (0e1855b5452)
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/utils/log/file_task_handler.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
