[Run Service] Ensure `WatchRuns` works expected

(5 comments) (0 reactions) (0 assignees)Python (378 forks)batch import

flyte2good first issue

Repository metrics

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)

Research direction: 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.
Tech stack: pythongrpc
Domain: backendapi
Issue type: Feature
Difficulty: 3
Estimated time: Half day
Activity status: Active
Clarity: Clear
Prerequisites: protobufgRPCFlyte run service basics
Newbie friendliness: 60