[FLINK-22543][runtime-web] Fix Exception History table layout broken by long error label strings

[Izeren]

What is the purpose of the change

On the Job > Exceptions > Exception History tab, long error labels cause the Time column to collapse to near-zero width. Text wraps character-by-character vertically, making the entire row unreadable. The table also extends beyond the viewport with no horizontal scrollbar.

Similar issue was reported in FLINK-22543 where Flink SQL task names exacerbate the problem.

Brief change log

• Set nzTableLayout="fixed" on the Exception History <nz-table> so columns respect their declared widths regardless of content
• Add percentage-based column widths for Time (12%), Task Name (18%), Location (12%), and the expand toggle (4%); Exception takes the remaining ~54%
• Add word-break: break-all on the exception cell to force mid-word line wrapping for long unspaced strings
• Style nz-tag elements inside the exception cell with max-width: 100% and white-space: normal to prevent tag overflow
• Change .exception-select from fixed width: 300px to width: 100% so the dropdown fills available cell space under fixed layout

Verifying this change

Manually verified with a minicluster producing long exception strings at multiple viewport sizes (4K 27", 16" laptop, heavily squashed window).

Example before the fix:

Examples after the fix:

27 inch: (width="2288" height="810")

16 inch: (width="1448" height="946")

somewhat squashed: (width="610" height="804")

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

---

Was generative AI tooling used to co-author this PR?

• Yes — Claude Code (Claude Opus 4.6)

Generated-by: Claude Code (Claude Opus 4.6)

[flinkbot]

CI report:

• e4a5f19 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[spuru9]

LGTM — scoped, well-verified across viewport sizes. Thanks for the screenshots.

[rkhachatryan]

LGTM, thanks for the fix!