sdk-v2.0.0,otel-v1.0.0 #711
yaythomas
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
aws-durable-execution-sdk-python v2.0.0
This is a major release. It contains breaking changes. If you are upgrading from 1.x, read the 1.x to 2.0 migration guide. The guide covers every breaking change below with before and after code.
Breaking Changes
CallableRuntimeError,UserlandError,CallableRuntimeErrorSerializableDetailsremoved (136976d, feat(errors): typed per-operation error hierarchy #540)CallbackErrorout of the termination tree (c089f9f, feat(errors): Add graded callback error types #563)SerDesErrorinstead ofExecutionError; first-run serialize/deserialize round trip for step, child contexts, map/parallel, and wait_for_condition;RetryableSerDesErroradded (d527f19 fix(step): Return round-tripped result on first run #543, caa57ad fix: round-trip serdes result on first run across ops #550)map/parallel:max_concurrencybounds in-flight branches, config validation at construction and call time,all_completed()now tolerates all failures,BatchResult.allomits never-started branches, summary payloads use an SDK-owned envelope (fdc952b)type,sub_type,name,parent_id); mismatches raiseNonDeterministicExecutionError(38d94dc, fix(core): validate replay operation identity #698)wait_for_conditionraisesWaitForConditionErroron exhaustion;WaitDecisionandWaitStrategyConfig.timeoutremoved (e77a53e)wait_for_conditionfails on unreadable polling state instead of restarting frominitial_state(c183ec8)InvokeConfig.timeout/timeout_secondsremoved (a982efa, fix: remove timeout from Invoke Config #340)ItemBatcher,ItemsPerBatchUnit,BatchedInput,TerminationMode,StepFuture,MapConfig.item_batcher,ChildConfig.item_serdes,ChainedInvoke*enums (6a89b70)Features
should_completecustom completion predicate formap/parallel, withcomplete_batch/continue_batch,CompletionOutcome,CompletionStatus, andBatchCompletionError(d4090f1, feat: add should_complete to CompletionConfig #605)attemptexposed onStepContextandWaitForConditionCheckContext(6aa6a02, feat: expose operation attempt in contexts #549)PluginLoadError(808e9a8, feat: auto-discover instrumentation plugins #620); plugin interface stabilization (c93073f, feat(plugin): stabilize plugin interface and otel package #625) — interface remains experimentalBug Fixes
Docs
aws-durable-execution-sdk-python-otel v1.0.0
First stable release of the OpenTelemetry plugin, built for SDK 2.0. Requires
aws-durable-execution-sdk-python>=2.0.0.Documentation: OpenTelemetry plugin and plugin interface.
Changes since 0.3.0
[standalone]extra outside layers (fix(otel): rely on Lambda layers for OpenTelemetry dependencies #651). OpenTelemetry upper bounds removed (fix(otel): remove OpenTelemetry upper bounds #609)OtelPluginConfigis fully enum-driven (feat(otel): fully enum-driven OtelPluginConfig #612); instrumentation enums decoupled from the Lambda service (feat(plugin): decouple instrumentation enums from lambda service #634)faas/cloudattributes dropped from the invocation span (feat(otel): drop faas/cloud attrs from invocation span #596)Features
ExecutionOtelPluginwith a Workflow-rooted trace hierarchy (feat(otel): add ExecutionOtelPlugin with Workflow-rooted trace hierarchy #576) and a Workflow span onInvocationOtelPlugin(feat(otel): add Workflow span to InvocationOtelPlugin #593)execution_start_timeon invocation info (feat(plugin)!: add execution_start_time to invocation info #561)Bug Fixes
What's Changed
New Contributors
Full Changelog: sdk-v1.7.0,otel-v0.3.0...sdk-v2.0.0
This discussion was created from the release sdk-v2.0.0,otel-v1.0.0.
All reactions