Skip to content

Reject overflowing metric timestamp offsets - #16341

Open
tamird wants to merge 1 commit into
google:masterfrom
tamird:delivery/metricsviz-time-offset-bounds
Open

tamird wants to merge 1 commit into
google:masterfrom
tamird:delivery/metricsviz-time-offset-bounds

Conversation

@tamird

@tamird tamird commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

Metricsviz accepts unsigned 64-bit nanosecond offsets, then converts them
to time.Duration. Offsets above MaxInt64 become negative and place samples
before the collection start instead of rejecting the invalid log.

Limit offsets to the nonnegative time.Duration range and retain the
parser's range error. Check the valid endpoints and overflowing values
through the existing metrics log parser.

The standalone parser suite passes, but its analyzer build encounters an
existing Docker protobuf dependency error 1. Both analyzer owners pass
for AMD64 and ARM64 with the separate #16098 build-graph correction 2.
This PR contains only the timestamp change.

Metricsviz accepts unsigned 64-bit nanosecond offsets, then converts them
to time.Duration. Offsets above MaxInt64 become negative and place samples
before the collection start instead of rejecting the invalid log.

Limit offsets to the nonnegative time.Duration range and retain the
parser's range error. Check both valid endpoints and overflowing values
through the existing metrics log parser.

Assisted-by: OpenAI Codex
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant