Skip to content

Record activity schedule-to-start in run_until() - #298

Merged
rmcdaniel merged 1 commit into
mainfrom
fix/general-188-run-until-activity-metric
Nov 11, 2026
Merged

rmcdaniel merged 1 commit into
mainfrom
fix/general-188-run-until-activity-metric

Conversation

@rmcdaniel

Copy link
Copy Markdown
Member

Found by today's installed check for #188 (published SDK 2.15.1 against published Native Server 3.4.0). Workflow tasks recorded durable_workflow_worker_task_schedule_to_start_seconds, but activity tasks recorded 0 samples under Worker.run_until(). run_until() runs activities through _run_until_activity_task, which never called _record_task_schedule_to_start. Only run()'s _dispatch_activity_task did. Native sends ready_age_ms correctly; this is SDK-only.

  • One-line fix plus a comment in _run_until_activity_task.
  • New test test_run_until_activity_records_server_ready_age.
  • Local run: ruff clean, tests/test_sdk_metrics_contract.py 123 passed.

Refs #188.

🤖 Generated with Claude Code

run_until() runs activity tasks through _run_until_activity_task, which
skipped the schedule-to-start sample that run()'s dispatch path records.
Found by an installed check against published Native Server 3.4.0 (#188).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@rmcdaniel
rmcdaniel merged commit 0c82812 into main Nov 11, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant