Skip to content

chore(weave): remove dead actions_execute_batch endpoint and ActionSpec#6987

Open
gtarpenning wants to merge 2 commits into
masterfrom
gtarpenning/delete-actions-execute-batch
Open

chore(weave): remove dead actions_execute_batch endpoint and ActionSpec#6987
gtarpenning wants to merge 2 commits into
masterfrom
gtarpenning/delete-actions-execute-batch

Conversation

@gtarpenning
Copy link
Copy Markdown
Member

Summary

  • /actions/execute_batch and the ActionSpec / LLM Judge / contains-words executor were the Nov 2024 "Online Evals Part 1" stub (chore(weave): Online Evals Part 1: Backend support for on-demand LLM Judges #2882). Part 4 never landed.
  • Online evals in prod go through /calls/score -> Kafka -> call_scoring_worker, which does not touch this code.
  • Frontend has no live caller; the LLM_JUDGE option in NewScorerDrawer is unconditionally filtered out and LLMJudgesTab is not mounted on ScorersPage. Companion core PR (wandb/core) removes the frontend dead code, the FastAPI route, and the worker wrappers.

Drops:

  • weave/trace_server/actions_worker/ (dispatcher + llm_judge + contains_words)
  • weave/trace_server/interface/builtin_object_classes/actions.py (ActionSpec + configs)
  • actions_execute_batch from interface + CH + sqlite + adapter + remote bindings + test fixtures
  • ActionsExecuteBatchReq / ActionsExecuteBatchRes
  • ActionSpec registration in builtin_object_registry + weave.trace.base_objects export
  • tests/trace/test_actions_lifecycle.py, tests/integrations/litellm/test_actions_lifecycle_llm_judge.py
  • stale generated_base_object_class_schemas.json (unreferenced legacy artifact)

Regenerated generated_builtin_object_class_schemas.json (12 objects, down from 13).

Customer DBs may contain historical ActionSpec rows. They will no longer round-trip through the SDK's typed BUILTIN_OBJECT_REGISTRY but will still be readable as plain objects.

Testing

imported all touched servers (CH, sqlite, adapter, remote_http, stainless) and confirmed ActionSpec no longer in registry, ActionsExecuteBatchReq no longer on tsi, actions_execute_batch no longer on CH server. ruff clean.

The `/actions/execute_batch` endpoint and its `ActionSpec` / LLM Judge /
contains-words executor were the Nov 2024 "Online Evals Part 1" stub. The
async Part 4 never landed, and the production online-evals path now goes
through `/calls/score` -> Kafka -> call_scoring_worker, which doesn't touch
this code. Frontend has no live caller. Safe to remove.

Drops:
- weave/trace_server/actions_worker/ (dispatcher + judge/contains-words impls)
- weave/trace_server/interface/builtin_object_classes/actions.py (ActionSpec)
- actions_execute_batch method from interface + CH + sqlite + adapter + both
  remote bindings + test fixtures
- ActionsExecuteBatchReq/Res request models
- ActionSpec registration in builtin_object_registry + base_objects export
- tests/trace/test_actions_lifecycle.py
- tests/integrations/litellm/test_actions_lifecycle_llm_judge.py
- stale generated_base_object_class_schemas.json (unreferenced legacy file)

Regenerated generated_builtin_object_class_schemas.json (12 objects, was 13).
@codecov
Copy link
Copy Markdown

codecov Bot commented May 28, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@wandbot-3000
Copy link
Copy Markdown

wandbot-3000 Bot commented May 28, 2026

@gtarpenning gtarpenning marked this pull request as ready for review May 28, 2026 15:49
@gtarpenning gtarpenning requested a review from a team as a code owner May 28, 2026 15:49
@gtarpenning gtarpenning enabled auto-merge (squash) May 28, 2026 16:24
@gtarpenning gtarpenning disabled auto-merge May 28, 2026 16:25
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.

2 participants