Deterministic explain should allow users to see full failure messages rather than truncated ones

[s-sajid-ali]

Within the explain view, the actual error messages are truncated to 120 characters:

sofka/src/explain.rs

Lines 541 to 550 in bec07a9

	/// Join a condition's reason and message into `Reason: message`, dropping
	/// whichever is empty.
	fn join_reason(reason: &str, msg: &str) -> String {
	match (reason.is_empty(), msg.is_empty()) {
	(false, false) => format!("{reason}: {}", truncate(msg, 120)),
	(false, true) => reason.to_string(),
	(true, false) => truncate(msg, 120),
	(true, true) => "(no detail)".into(),
	}
	}

Sometimes, this defeats the ability of deterministic explain feature of sofka where I have to go back to a YAML view to get the messages or use kubectl directly. Case in point, I was trying to figure out a basic knative serving error from a deployment description and my truncated error message was:

│    ReplicaFailure: FailedCreate: pods "helloworld-python-00001-deployment-....-...." is forbidden: failed quota: ...-quota: must …                    │

the most relevant part that was discarded by truncation was:

specify limits.cpu for: queue-proxy; limits.memory for: queue-proxy; requests.memory for: queue-proxy

While I appreciate the ability to get this error directly from the deployment investigate view (instead of investigating the messages from the corresponding replicaset), the truncated error message makes the feature less useful than it could be.

Could line wrapping toggle be enabled for this instead of an arbitrary character limit? Thanks!

PS: Thanks for creating this tool!

[nklmilojevic]

Agreed, thanks for the report and the concrete example! Cutting the message is the opposite of what explain is for - the part that tells you what to fix is usually at the end.

I'll treat it as a bug:

• drop the 120/100 char truncation on condition, event and container messages
• wrap long findings in explain by default, with a hanging indent so wrapped lines stay under their finding
• w toggles back to clipped lines if you want the dense overview, same key as the YAML/describe/log views

The GitOps views share the same renderer, so long Flux and Argo CD messages get fixed too :)

[nklmilojevic]

fixed in #767

[s-sajid-ali]

Thanks for fixing this!