Repository navigation
docs(runs): correct the spot interruptions comment in TaskView [COMP-1658] - #740
Conversation
AWS Batch and Google Batch count real spot interruptions, so they do not report 0 on every task as the comment claimed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Approve: a one-line comment fix with no change in behaviour.
The diff only rewords the comment above the numSpotInterruptions check in TaskView.toString. The old comment said AWS and Google Batch report 0 on every task, which contradicts the code right below it: the row appears only when the value is greater than 0. The new wording ("Most tasks report 0") matches what the code does. The code itself is unchanged.
There was a problem hiding this comment.
🟢 Approval recommended
There are no active review issues for the comment-only clarification of why zero-count spot-interruption rows are hidden.
No open issues 🎉
What changed in this PR
Corrects the comment above the Spot interruptions row in TaskView, removing the inaccurate claim that AWS Batch and Google Batch always report zero interruptions.
Changes:
- Clarifies why zero-count rows are hidden; runtime behavior remains unchanged.
| File | Description |
|---|---|
src/main/java/io/seqera/tower/cli/responses/runs/tasks/TaskView.java |
Corrects the spot-interruption comment without changing display logic. |
Review effort: Balanced
Summary
Spot interruptionsrow inTaskView, added in feat(runs): show spot interruptions in task view [COMP-1658] #739. It said AWS Batch and Google Batch report 0 on every task; they count real spot interruptions (Nextflow 26.04.0 or later). The row is still hidden at 0 because most tasks report 0.Comment only, no behaviour change. Jira: COMP-1658.
🤖 Generated with Claude Code