[Run Service] Ensure `GetActionDetails` works expected

[machichima]

Command

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

Response

Field	Expected	Presented?	Need implement?
details	ActionDetails	✅	❌
details.id	ActionIdentifier	✅	❌
details.metadata	ActionMetadata	❌	✅
details.status	ActionStatus	✅	❌
details.status.phase	ActionPhase	✅	❌
details.status.start_time	Timestamp	✅	❌
details.status.end_time	optional Timestamp	❌	✅ (available when the action terminated)
details.status.attempts	uint32	✅	❌
details.status.cache_status	CatalogCacheStatus	❌	✅
details.status.duration_ms	optional uint64	❌	✅ (available when the action terminated)
details.error_info	oneof result	❌	✅
details.abort_info	oneof result	❌	✅
details.spec.task	oneof spec	❌	✅
details.spec.trace	oneof spec	❌	✅
details.attempts	repeated ActionAttempt	✅	❌
details.attempts[].phase	ActionPhase	✅	❌
details.attempts[].start_time	Timestamp	✅	❌
details.attempts[].end_time	optional Timestamp	❌	✅ (available when the action terminated)
details.attempts[].error_info	optional ErrorInfo	❌	✅
details.attempts[].attempt	uint32	✅	❌
details.attempts[].log_info	repeated TaskLog	❌	✅
details.attempts[].outputs	OutputReferences	❌	✅
details.attempts[].logs_available	bool	❌	✅
details.attempts[].cache_status	CatalogCacheStatus	❌	✅
details.attempts[].cluster_events	repeated ClusterEvent	❌	✅
details.attempts[].phase_transitions	repeated PhaseTransition	✅	❌
details.attempts[].cluster	string	❌	✅
details.attempts[].log_context	LogContext	❌	✅

[runllm]

Based on the available data sources, the GetActionDetails method returns an ActionDetails object with fields such as id, status, phase, start_time, attempts, and more. However, not all fields listed in your table are currently presented or implemented. Specifically, fields like metadata, status.end_time, status.cache_status, status.duration_ms, error_info, abort_info, spec.task, spec.trace, and several fields within attempts[] (e.g., end_time, error_info, log_info, outputs, logs_available, cache_status, cluster_events, cluster, log_context) are not explicitly documented as available or implemented in the current API reference or code examples. These missing fields would require additional implementation to be fully supported as per your expectations.

For the fields that are available, you can retrieve them using the ActionDetails class and its properties/methods, as described in the API reference and code. For example, you can access id, status, phase, start_time, and attempts directly. If you need more detail on which fields are present in the protobuf or how to access them programmatically, let me know and I can break down the reasoning step-by-step.

Sources:

• ActionDetails API Reference
• ActionDetails Class (BYOC)
• ActionDetails Source Code

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!