🤖 Filed by agent.
Summary
The GetTaskLogs RPC on ControllerService is now a thin forwarding shim to FetchLogs. All internal callers have been migrated to use FetchLogs with LIKE patterns directly.
What to remove (after 2026-05-01)
-
Proto (lib/iris/src/iris/rpc/cluster.proto):
Controller.GetTaskLogsRequest message
Controller.TaskLogBatch message
Controller.GetTaskLogsResponse message
rpc GetTaskLogs(...) from ControllerService
-
Controller service (lib/iris/src/iris/cluster/controller/service.py):
get_task_logs forwarding method
-
Dashboard types (lib/iris/dashboard/src/types/rpc.ts):
- Any remaining
TaskLogBatch / GetTaskLogsResponse references
-
Regenerate proto/connect code after proto cleanup
Context
The FetchLogs RPC now supports SQL LIKE patterns in the source field (e.g. /user/job/%), making GetTaskLogs' job/task ID parsing redundant. The child_job_statuses field on GetTaskLogsResponse is no longer populated.
🤖 Filed by agent.
Summary
The
GetTaskLogsRPC onControllerServiceis now a thin forwarding shim toFetchLogs. All internal callers have been migrated to useFetchLogswith LIKE patterns directly.What to remove (after 2026-05-01)
Proto (
lib/iris/src/iris/rpc/cluster.proto):Controller.GetTaskLogsRequestmessageController.TaskLogBatchmessageController.GetTaskLogsResponsemessagerpc GetTaskLogs(...)fromControllerServiceController service (
lib/iris/src/iris/cluster/controller/service.py):get_task_logsforwarding methodDashboard types (
lib/iris/dashboard/src/types/rpc.ts):TaskLogBatch/GetTaskLogsResponsereferencesRegenerate proto/connect code after proto cleanup
Context
The
FetchLogsRPC now supports SQL LIKE patterns in thesourcefield (e.g./user/job/%), makingGetTaskLogs' job/task ID parsing redundant. Thechild_job_statusesfield onGetTaskLogsResponseis no longer populated.