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 9e236ae0778 feat(providers/amazon): add airflow 3 compat logic
omit 777c9a211cf test(providers/amazon): fix
TestCloudwatchTaskHandler::test_read
omit 10043f1864c test(providers/elasticsearch): fix part of the existing
unit test
omit 201e99df9eb feat(api_connexion/log): update v1 api to the latest log
format
omit e228104c1da test(api_fastapi): fix existing test_log unit tests
omit 4b49860a3e2 test(www): fix existing unit tests
omit 50a4427e979 test(test_log_reader): fix existing unit tests
omit 2361547fa36 style: improve type annotation
omit 926c31ca0f5 style: reduce if-else and directly use bool for assigning
metadata["download_logs"]
omit 6dee2dd047e style: group metadata pop
omit af7b908e761 Fix typescript useLogs
omit 8f4fe3a6f6c Render structured logs in the new UI rather than showing
raw JSON
add a54d1d9a2eb Add dependencies section to gcp cloud build instance
response (#46947)
add befc9dc9a8c Render structured logs in the new UI rather than showing
raw JSON
add 9c3bc500c9d Fix typescript useLogs
add 480594da168 style: group metadata pop
add a4c29d1f2eb style: reduce if-else and directly use bool for assigning
metadata["download_logs"]
add 14c29d35998 style: improve type annotation
add f262d404bda test(test_log_reader): fix existing unit tests
add be336f964ad test(www): fix existing unit tests
add 8d512a5ed34 test(api_fastapi): fix existing test_log unit tests
add 6a11a857110 feat(api_connexion/log): update v1 api to the latest log
format
add 95fa23a407f test(providers/elasticsearch): fix part of the existing
unit test
add 323b97ca069 test(providers/amazon): fix
TestCloudwatchTaskHandler::test_read
add c2561b3d1b0 feat(providers/amazon): add airflow 3 compat logic
add dd1c6770e06 feat(providers/google): 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 (9e236ae0778)
\
N -- N -- N refs/heads/render-json-logs-new-ui (dd1c6770e06)
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/google/cloud/log/gcs_task_handler.py | 16 ++++--
.../unit/google/cloud/log/test_gcs_task_handler.py | 60 +++++++++++++++-------
.../unit/google/cloud/triggers/test_cloud_build.py | 1 +
3 files changed, 54 insertions(+), 23 deletions(-)
