fix(stats): keep omen-alpha under unknown provider - #47248
Merged
Conversation
opencode-agent
Bot
changed the title
|
whahahaha |
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
2 participants
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.
Issue for this PR
Requested provider attribution change; no separate issue.
Type of change
What does this PR do?
Keep
omen-alphain stats, but always attribute it tounknown. This replaces the earlier exclusion proposal.Use the same stealth-model list in the SQL aggregation queries and TypeScript normalization, checking it before route-model author detection or provider fallback. Model, provider, geographic, and retention aggregates retain usage without attributing it to an underlying provider. Other models keep their existing attribution rules.
No inference or billing changes. Deployment and a stats refresh are still required; this PR does not restore previously deleted rows or purge cached pages.
How did you verify your code works?
From
packages/stats/core:bun test src/domain— 15 passing tests. Regression coverage checks route/provider overrides, normalized suffixes, retained metrics, and precedence in stats/retention SQL. The new expectations failed against the earlier exclusion implementation.bun typecheck— passed.git diff --check— passed.Screenshots / recordings
Not applicable; no UI changes.
Checklist
Requested by: @fwang (Frank via Slack)