[Run Service] Ensure `WatchRuns` works expected

(5 条评论) (0 个反应) (0 位负责人)Python (378 个派生)batch import

flyte2good first issue

仓库指标

SCOPE=project bash runs/test/scripts/watch_runs.sh

Field	Expected	Presented?	Need implement?
`runs`	`repeated Run`	✅	❌
`runs[].action`	`Action`	✅	❌
`runs[].action.id`	`ActionIdentifier`	✅	❌
`runs[].action.id.run.org`	`string`	✅	❌
`runs[].action.id.run.project`	`string`	✅	❌
`runs[].action.id.run.domain`	`string`	✅	❌
`runs[].action.id.run.name`	`string`	✅	❌
`runs[].action.id.name`	`string`	✅	❌
`runs[].action.metadata`	`ActionMetadata`	✅	❌
`runs[].action.status`	`ActionStatus`	✅	❌
`runs[].action.status.phase`	`ActionPhase`	✅	❌
`runs[].action.status.start_time`	`Timestamp`	❌	✅
`runs[].action.status.end_time`	`optional Timestamp`	❌	✅ (available when the action terminated)
`runs[].action.status.attempts`	`uint32`	❌	✅
`runs[].action.status.cache_status`	`CatalogCacheStatus`	❌	✅
`runs[].action.status.duration_ms`	`optional uint64`	❌	✅ (available when the action terminated)

研究方向: The issue requires implementing missing fields in the WatchRuns response. Start by examining the protobuf definitions for Run and related messages in the repository. The test script at runs/test/scripts/watch runs.sh shows the expected structure. Review the implementation of WatchRuns in the service code to add the missing fields like start time, end time, attempts, cache status, duration ms.
技术栈: pythongrpc
领域: backendapi
议题类型: 功能
难度: 3
预计时间: 半天
活动状态: 活跃
清晰度: 清晰
前置要求: protobufgRPCFlyte run service basics
新手友好度: 60