This is an automated email from the ASF dual-hosted git repository.
kaxil pushed a change to branch durable-default-on
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 48b36c9042a Skip the fallback-model durable refusal case on
pydantic-ai-slim before 2.64
discard 933963417e3 Keep agent tasks running when pydantic-ai refuses their
default durable run
discard 13ef5a3da64 Word durable execution's refusals for tasks that never set
durable=True
discard 913c449a79e Rename the agent operator's per-run durable flag apart
from its argument
discard 4a5ba8995a3 Delete a stale tool approval transcript on every fresh
agent run
discard e9ffb78abee Turn on durable execution by default for agent tasks that
can retry
omit 14c265b3663 Fix a rejected review answer replaying after a killed
attempt
omit 0aa8949f191 Reflow the HITL review paragraph on retries after the
review started
omit c4f3e5b1945 Name the HITL review helpers after what they do
omit 8899d0ea9f2 Fix durable agent runs replaying stale steps after a
first-attempt pause
omit 47fc7a1d006 Let durable agent tasks use HITL review
omit 9c2f16ff659 Merge branch 'hitl-review-park' into durable-hitl-review
omit 374bc9332f3 Release the worker slot while an AgentOperator HITL review
waits
add 2935fcb9fbb Go SDK: read the Dag run conf into a struct with typed
fields (#75602)
add 4c20f4ca486 Park HITL reviews between rounds and let durable agent
tasks use them (#76916)
add b0d09e5fdfb Turn on durable execution by default for agent tasks that
can retry
add c8345ec3708 Delete a stale tool approval transcript on every fresh
agent run
add e5755b815b0 Rename the agent operator's per-run durable flag apart
from its argument
add d364448efa7 Word durable execution's refusals for tasks that never set
durable=True
add 7402dcbf701 Keep agent tasks running when pydantic-ai refuses their
default durable run
add 2f5f6573e4d Skip the fallback-model durable refusal case on
pydantic-ai-slim before 2.64
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 (48b36c9042a)
\
N -- N -- N refs/heads/durable-default-on (2f5f6573e4d)
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:
.../authoring-and-scheduling/language-sdks/go.rst | 33 +-
.../reports.go => internal/fieldname/fieldname.go} | 19 +-
go-sdk/pkg/binding/binding.go | 11 +-
go-sdk/sdk/conf.go | 385 +++++++++++++++++++++
go-sdk/sdk/conf_test.go | 353 +++++++++++++++++++
go-sdk/sdk/context.go | 2 +
6 files changed, 786 insertions(+), 17 deletions(-)
copy go-sdk/{cmd/airflow-go-pack/testdata/multidag/reports/reports.go =>
internal/fieldname/fieldname.go} (59%)
create mode 100644 go-sdk/sdk/conf.go
create mode 100644 go-sdk/sdk/conf_test.go