Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Medium
threads/thread-list-v2-items.tsx:784Failed rows now render the machine glyph whenever
environmentLabelandenvironmentMachineare present, including failures withoutlastError; this regresses the intended failed-row presentation. Restore thestatus !== "failed"guard on the glyph condition.🚀 Reply "fix it for me" or copy this AI Prompt for your agent:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a regression. The glyph now lives inside the
thread.branch || environmentLabelbranch, which only renders whenstatus === "failed" && lastErroris false, so a failed row that has an error message still shows the red text and no glyph, exactly as before. A failed row without an error message never had a distinct presentation: the old code also fell through to the "branch · env" line and drew the label, and the oldstatus !== "failed"guard only suppressed the icon next to that label. Drawing the label without its glyph was an accidental asymmetry, so the glyph following the label whenever the label renders is the intended behavior.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does change failed rows without
lastError: the previous explicit guard hid their glyph. I found no evidence that removing that distinction was intended, so the original concern stands.