Skip to content

fix(otel): correct exported status mappings - #752

Open
zhongkechen wants to merge 1 commit into
mainfrom
fix/otel-status-mappings
Open

zhongkechen wants to merge 1 commit into
mainfrom
fix/otel-status-mappings

Conversation

@zhongkechen

Copy link
Copy Markdown
Contributor

Fixes #750.

Both OTel views now reserve operation OK for SUCCEEDED. Cancelled, timed-out, stopped and failed outcomes without error details stay UNSET; delivered error details still produce ERROR and the existing exception event. Retry invocations export durable.invocation.status=RETRYING while the core InvocationStatus.RETRY API is unchanged. The OTel README documents these attribute corrections.

Validation: 292 OTel tests pass, including 42 new cases across both views for terminal statuses with/without errors, operations started in this or a previous invocation, and retry followed by resume with context restoration. The new tests reproduce 18 failures on unmodified main. hatch run dev-otel:typecheck, package hatch fmt --check, and git diff --check pass. Tests use real OTel providers/exporters in process; no cloud deployment was run. Shared conformance status requirements can be coordinated separately.

Based directly on main; independent of the breaking plugin-factory migration in #737.

@zhongkechen
zhongkechen deployed to ai-pr-review-runtime October 2, 2026 20:38 — with GitHub Actions Active
@zhongkechen
zhongkechen deployed to ai-pr-review-runtime October 2, 2026 20:38 — with GitHub Actions Active
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Codex AI review

No actionable findings. Coverage spans both OTel plugin views; residual risk is limited to exporter-specific behavior not exercised in a deployed environment.

Reviewed commit 79f94f53235576d2da459710204de5ec39655f39. Workflow run

This branch was successfully deployed

1 active deployment
ai-pr-review-runtime — 79f94f53 Deployed Oct 2, 2026 by zhongkechen via ai-pr-review / Codex review / Generate Codex review #1152
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: OTel status mapping marks cancelled/timed-out operations OK and emits RETRY instead of RETRYING

1 participant