flyteorg/flyte

[Run Service] Ensure `WatchRunDetails` works expected

Open

#6978 opened on Mar 6, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Python (3,705 stars) (378 forks)batch import
flyte2good first issue

Description

Command

RUN_NAME=run-1772757248 bash runs/test/scripts/watch_run_details.sh

Response

Field Expected Presented? Need implement?
details RunDetails ✅ ❌
details.run_spec task.RunSpec ❌ ✅
details.action ActionDetails ❌ ✅
details.action.id ActionIdentifier ❌ ✅
details.action.metadata ActionMetadata ❌ ✅
details.action.status ActionStatus ❌ ✅
details.action.status.phase ActionPhase ❌ ✅
details.action.status.start_time Timestamp ❌ ✅
details.action.status.end_time optional Timestamp ❌ ✅ (available when the action terminated)
details.action.status.attempts uint32 ❌ ✅
details.action.status.cache_status CatalogCacheStatus ❌ ✅
details.action.status.duration_ms optional uint64 ❌ ✅ (available when the action terminated)
details.action.error_info oneof result ❌ ✅
details.action.abort_info oneof result ❌ ✅
details.action.spec.task oneof spec ❌ ✅
details.action.spec.trace oneof spec ❌ ✅
details.action.attempts repeated ActionAttempt ❌ ✅

Contributor guide

Tech stack
gogrpc
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go language basicsgRPC conceptsFlyte RunService protobuf
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the existing protobuf definitions for RunDetails, RunSpec, ActionDetails, etc. in the Flyte repository. Look at the current implementation of the WatchRunDetails endpoint in the RunService to understand how fields like `details` are populated. Follow the same pattern to implement the missing fields `details.run spec`, `details.action`, and all its subfields as listed in the table. Ensure the response correctly includes each required field with the appropriate type.