Skip to content

Reword the reason for the Arize sample's temporalio pin #421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DABH merged 2 commits into from
Nov 14, 2026
Merged

Reword the reason for the Arize sample's temporalio pin #421

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f12d138
Reword the reason for the Arize sample's temporalio pin
DABH Nov 14, 2026
ff6bac5
Drop "currently" from the README's reset note
DABH Nov 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion arize_tracing/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ temporal workflow reset --workflow-id <workflow id> --type FirstWorkflowTask --r
uv run verify_trace.py --workflow-id <workflow id> --expect-runs 2
```

The reset case currently needs temporalio 1.36.0 exactly (see PR #420).
The reset case needs temporalio 1.36.0 exactly (see PR #420).

![Activity retry attempts in Phoenix](phoenix-retry-attempts.png)

Expand Down
7 changes: 3 additions & 4 deletions arize_tracing/pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,9 @@ name = "temporalio-samples-arize-tracing"
version = "0.1.0"
requires-python = ">=3.11"
dependencies = [
# Pinned: 1.36.0 applies workflow activation jobs as a single batch, which
# keeps a reset's reapplied update from reusing a span ID of the original
# run. 1.36.1 (temporarily?) undoes that, so we're pinning to 1.36.0
# explicitly until a future release resolves this issue one way or another.
# 1.36.0 applies workflow activation jobs as a single batch, which keeps a
# reset's reapplied update from reusing a span ID of the original run.
# Later releases do not do this by default (temporalio/sdk-python#2121).
"temporalio[opentelemetry]==1.36.0",
# 1.1.0 fixes span parenting when one worker runs both workflows and
# activities; its openinference extra brings the Agents SDK instrumentation.
Expand Down
Loading