fix(workflows): send Statsig event time in milliseconds#69716
Open
clown6613 wants to merge 1 commit into
Open
Conversation
The claude-dedupe-issues workflow sent the Statsig `time` field as epoch seconds (`now | floor`) and as a string, while Statsig's /v1/log_event API expects epoch milliseconds as a number. The sibling workflow log-issue-events.yml already does this correctly via `$(date +%s)000`. Change to `now * 1000 | floor` so duplicate-comment events are timestamped in milliseconds, matching the sibling workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 21, 2026
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.
What
claude-dedupe-issues.ymlsent the Statsigtimefield as epoch seconds (now | floor) and as a string.Statsig's
/v1/log_eventAPI expectstimeas epoch milliseconds (number). The sibling workflowlog-issue-events.ymlalready does this correctly via$(date +%s)000.Why
As-is, every
github_duplicate_comment_addedevent is timestamped ~1000x in the past (1970-era when interpreted as ms), so events are misdated or dropped. This aligns the dedupe workflow with the sibling workflow's millisecond, numeric format.Spec reference
Per the Statsig Log Custom Events API,
timeaccepts a "unix timestamp in milliseconds or ISO date string", with the example value"time": 1616826986211(13-digit number). Epoch seconds is not an accepted format, and a numeric string (e.g."1781958740") is neither a millisecond number nor an ISO date string. The fix produces the documented numeric-millisecond form.Verification