Bug: Character display wraps due to improper width calculation for additional field with -tpa https

[gregeva]

What's the Problem

The problem is that here in a run when --threadpool-activity https is specified, the column to print that data has a maximum width calculated to the extreme end of the terminal line. This is not taking abiding by the pre-defined column widths in the %column_widths hash, and it is not leaving space for the next section which needs to be printed where the length is in $durations_graph_width.

Displaying the Issue

How to Reproduce

ltl -osum -bs 240 -n 5 -tpa https ./logs/AccessLogs/*-4.2026-01-26.*

[gregeva]

Investigation Findings

Root cause identified: The column layout system uses multiple overlapping data structures (%graph_width, @printed_column_widths, @printed_column_names, @printed_column_spacing) with inconsistent indexing. When threadpool activity columns are added via -tpa, the column name can be added to @printed_column_names without corresponding entries in the width/spacing arrays.

The immediate errors observed:

• Use of uninitialized value $max_length at line 2143
• Use of uninitialized value $width at line 2550
• Use of uninitialized value $printed_column_spacing[6] at lines 2554, 2573

Status: On Hold

A minimal fix is possible but would be fragile given the underlying architectural issues. A proper fix requires refactoring the column layout management system.

Blocked by: #33 (Refactor: Consolidate column width and layout management into unified data structure)

Once #33 is complete, this bug should be straightforward to resolve as part of that work.

[gregeva]

Status Update - 2026-01-31

Summary

Investigation complete. Root cause identified as architectural issue with column layout management (see comment above for details).

Resolution Path

This issue is blocked by #33 (Refactor: Consolidate column width and layout management into unified data structure).

The column layout refactoring must be completed first. Once #33 is resolved, the fix for this issue will be straightforward as part of that work - the new unified column management will prevent the array mismatch that causes this bug.

Workaround

Avoid using -tpa (threadpool activity) option until this is fixed. Other features work correctly.

[gregeva]

The root cause of this bug (fragile array-index coupling between @printed_column_widths, @printed_column_names, and @printed_column_spacing) has been eliminated by the column layout refactor (#33). All three arrays have been removed. Column properties are now stored in a single @column_layout array-of-hashes, making index mismatches impossible.

[gregeva]

Fixed by the column layout refactor (#33, branch 33-column-layout-refactor, release v0.12.0). The layout engine constrains all proportional columns within the terminal width, eliminating the unbounded width calculation that caused line wrapping.