Skip to content

feat: show what a failing object says about itself (#86) - #122

Merged
lex00 merged 1 commit into
mainfrom
feat/86-render-conditions
Aug 3, 2026
Merged

feat: show what a failing object says about itself (#86)#122
lex00 merged 1 commit into
mainfrom
feat/86-render-conditions

Conversation

@lex00

@lex00 lex00 commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

The behold half of chant#1401, and #86's last criterion.

chant#1397 made the status word honest — a crashlooping Pod reports CrashLoopBackOff rather than Running. chant#1401 adds the part that says what to do about it. This renders it:

health      degraded
status      Unschedulable
condition   PodScheduled=Unschedulable: 0/3 nodes are available:
            1 node(s) had untolerated taint.

Conditions sit with health and status rather than among the attributes below, because that is the answer — Unschedulable is the reason, and the message is what a person acts on. Rendering them through the generic attribute loop would have printed a JSON array at the bottom of the panel, which is where you put something nobody needs to read.

One line each, in the degraded colour. chant only sends conditions not in their happy state, so everything here is worth reading and there's nothing to filter. Absent on every substrate that records none, where the panel is unchanged.

395 tests pass, tsc clean, build clean.

Stacked behind chant#1402 landing — harmless before it, since an absent field renders nothing.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FBkcXzqjyY1YKWdaDFuqKs

The behold half of chant#1401, and #86's last criterion.

chant#1397 made the status word honest — a crashlooping Pod reports
`CrashLoopBackOff` rather than `Running`. chant#1401 adds the part that says
what to do about it, and this renders it:

    health      degraded
    status      Unschedulable
    condition   PodScheduled=Unschedulable: 0/3 nodes are available:
                1 node(s) had untolerated taint.

Conditions sit with health and status rather than among the attributes below,
because that IS the answer — `Unschedulable` is the reason, and the message is
what a person acts on. Rendering them through the generic attribute loop would
have printed a JSON array at the bottom of the panel, which is where you put
something nobody needs to read.

One line each, in the degraded colour. chant only sends conditions NOT in their
happy state, so everything here is worth reading and there is nothing to filter.
Absent on every substrate that records none, where the panel is unchanged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FBkcXzqjyY1YKWdaDFuqKs
@lex00
lex00 merged commit 3e5485b into main Aug 3, 2026
1 check passed
@lex00
lex00 deleted the feat/86-render-conditions branch August 3, 2026 04:44
@lex00 lex00 mentioned this pull request Aug 3, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant