feat: update AI metric reports 2026-06 - #4
Merged
Conversation
- jira: Lead Time/Cycle Time 추가, 이슈 건수 추이 차트 - pr: Merge Time 명칭 수정 - tokscale: 월별 토큰 사용 추이 차트 추가
t1000040
pushed a commit
that referenced
this pull request
Jul 10, 2026
…unhoyeo#737) * fix(antigravity-cli): date each turn by its per-generation timestamp parse_antigravity_cli_file stamped every gen_metadata row with the single session-created time from trajectory_metadata_blob.#2, and the module doc-comment claimed the per-turn proto carries only relative timings. It doesn't: each row carries an absolute {seconds, nanos} Timestamp at chatModel.#9.#4, the same wire shape session_created_ms already decodes. Without this, turns written into a conversation older than the live-tail window are stamped in the past and dropped from the live trace, and long conversations mis-bucket across midnight. Read chatModel.#9.#4 per row (via a shared proto_timestamp_ms) and fall back to the session-created time only when the field is absent or zero. Added per_generation_timestamp_overrides_session_fallback, which fails before the change. * fix(antigravity-cli): guard proto_timestamp_ms against i64 overflow A malformed protobuf can carry a Timestamp whose `seconds` varint is large enough that `seconds * 1000` overflows i64. With overflow-checks on (debug builds), the unchecked multiply panics instead of degrading to None, which breaks the module's malformed-data contract (every other decode path returns None on bad input). Switch to checked_mul/checked_add and return None on overflow. Regression test feeds a seconds varint of i64::MAX and asserts None without a panic, checks the in-range boundary (i64::MAX/1000) still decodes, and keeps a normal seconds+nanos stamp decoding to ms. * fix(antigravity-cli): range-validate Timestamp nanos in proto_timestamp_ms Reject `nanos` outside the protobuf Timestamp spec (0..=999_999_999), including values large enough to be negative once cast to i64. An out-of-range nanos now marks the whole stamp malformed (None) so the caller's `ms > 0` filter and session-timestamp fallback take over instead of producing a skewed per-turn time. Valid-input behavior is unchanged. Confidence: high Scope-risk: narrow --------- Co-authored-by: Junho Yeo <i@junho.io>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
변경 내용
6월 전체 실적 기준 (보정 없이 실측치)