fix(frontend): align log region column and disable selection on metadata

[jog1t]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[jog1t]

• refactor(frontend): runner_pool -> rivet_pool #5107
• refactor(frontend): modify onboarding for rivet compute #5106
• fix(frontend): align log region column and disable selection on metadata #5105 👈 (View in Graphite)
• fix(frontend): clickable namespaces in deployments table #5104
• fix(fontend): less monoscaped #5103
• fix(frontend): meaningful serverless metadata errors #5102
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[jog1t]

Merge activity

• May 26, 10:23 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 26, 10:31 PM UTC: Graphite rebased this pull request as part of a merge.
• May 26, 10:31 PM UTC: @jog1t merged this pull request with Graphite.

[claude]

PR #5105 Review: fix(frontend): align log region column and disable selection on metadata

Status: MERGED | +35 / -6 | 2 files changed

---

Overview

This PR fixes two UX issues in the deployment logs view:

1. Column alignment — the region label column width is now sized to the longest datacenter name, so log messages always start at the same horizontal position
2. Selection disabled — timestamps and region labels now have select-none so copying log content doesn't inadvertently grab metadata

---

Code Quality

Positive aspects:

• The +2 offset for brackets is explained inline with a comment — good.
• Using style for the dynamic gridTemplateColumns value is correct; Tailwind can't handle runtime-computed values.
• The empty <span /> placeholder when region is absent is a necessary correctness fix. Previously, returning null would collapse the grid to 2 columns, pushing the message into the region slot for region-less entries.
• The regionColumnWidth is only passed to data rows, not sentinel/loading rows — those return early before using it, so no issue there.

---

Concerns

1. Possible undefined crash on datacenters.reduce

// logs.tsx
const regionLabelLength = datacenters.reduce(
    (max, dc) => Math.max(max, dc.name.length),
    0,
);

If datacenters is undefined while the query is loading, this will throw. The diff doesn't show whether datacenters is guarded upstream. A defensive guard would be:

const regionLabelLength = (datacenters ?? []).reduce(
    (max, dc) => Math.max(max, dc.name.length),
    0,
);

2. Minor: comment typo

// Width all region labels to the longest datacenter name so messages line up.

Should be "Widen" not "Width".

3. Minor: "16ch" magic string duplicated

The fallback "16ch" appears in both deployment-logs.tsx (the width computation) and as the fallback in LogRowData. Not worth a constant for such a small change, but worth noting for future refactors.

---

Summary

The core logic is correct and the fix is minimal and focused. The main risk is the potential undefined crash on datacenters if the query hasn't resolved yet — worth verifying that the parent ensures a defined array before this line runs. The comment typo and duplicated default are cosmetic. Overall a clean, low-risk fix.