[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