Skip to content

[deep-report] Add NumericID type for mixed-type RunID/RunNumber any fields in logs_models.go #54533

Description

@github-actions

Description

pkg/cli/logs_models.go:358-359 types RunID any / RunNumber any on the aw_info.json-derived struct, while sibling structs in the same file type the equivalent field as int64 (:123, :280) or string (:329) — a real runtime ambiguity, not just a style nit. Root cause: ${{ github.run_id }} serializes as either a JSON number or a templated string depending on the producing step, so call sites scatter %v/fmt.Sprintf formatting to cope. Verified live at all cited lines.

Expected Impact

A single NumericID type with a custom UnmarshalJSON accepting both number and string forms (normalizing to int64) removes the scattered ad-hoc formatting/type-switching at every call site that reads RunID/RunNumber.

Suggested Agent

Copilot coding agent — add the NumericID type, wire it into logs_models.go, update call sites that currently type-switch or %v-format these fields.

Estimated Effort

Quick (1-2 hours)

Data Source

DeepReport analysis, 2026-08-21 cycle, sourced from discussion #54506 (Typist - Go Type Consistency Analysis), Untyped Usages Category 2. No existing open issue found covering this specific mixed-type field.

Generated by 🔬 Deep Report · agent · 186.6 AIC · ⌖ 14.7 AIC · ⊞ 11.9K ·

  • expires on Aug 23, 2026, 4:35 AM UTC-08:00

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions