[Run Service] Ensure `WatchRuns` works expected

(5 commentaires) (0 réaction) (0 personne assignée)Python (378 forks)batch import

flyte2good first issue

Métriques du dépôt

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)

Direction de recherche: 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.
Stack technique: pythongrpc
Domaine: backendapi
Type d'issue: Fonctionnalité
Difficulté: 3
Temps estimé: Une demi journée
Statut d'activité: Active
Clarté: Claire
Prérequis: protobufgRPCFlyte run service basics
Accessibilité débutant: 60