nextflow-io/nextflow

COLUMNS environment variable not honored

Open

#6,274 建立於 2025年7月14日

在 GitHub 查看
 (0 留言) (2 反應) (0 負責人)Groovy (3,382 star) (784 fork)batch import
good first issue

描述

Bug report

See discussion at the forum: https://community.seqera.io/t/output-width/2170

Expected behavior and actual behavior

ANSI output do not honor the COLUMNS variable set by bash. That causes issues in the expected width when the user want to change it for whatever reason, either to make it smaller than the actual available space or just to set a desired width in non-interactive executions.

Steps to reproduce the problem

Run any pipeline with long process names under SLURM and look at the standard output. Alternatively, try to change the width when running the process: COLUMNS=50 nextflow run ...

Program output

The output will be 80 characters wide in the SLURM execution and whatever your terminal sizes in the interactive execution. The expectation would be that using the COLUMNS environment variable, the width would be the one stored there.

Environment

  • Nextflow version: 25.04.2
  • Java version: 17.0.3.1 2022-04-22 LTS
  • Operating system: GNU/Linux (3.10.0-1160.88.1.el7.x86_64)
  • Bash version: 5.1.0(1)-release

Additional context

貢獻者指南

技術棧
無
領域
cli
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Basic knowledge of Groovy/JavaUnderstanding of environment variables
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
Investigate how Nextflow currently determines output width. Look for usage of tty or stty in the codebase. The COLUMNS environment variable should be checked before falling back to default 80. Refer to the community discussion at the provided forum link for more context.