Repository navigation
Scope quota windows by producer instance - #1583
Conversation
|
@kody start-review |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
9cb9b19 to
777091b
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@kody start-review |
This comment has been minimized.
This comment has been minimized.
|
Use two literal spaces after the period in the PR description, or the required form when the renderer would collapse the gap. Kody rule violation: Use two spaces between sentences in every human-facing string and agent-written paragraph |
|
❌ Error processing validation An error occurred while processing the system response. Please try again. Details
|
Load latest quota rows with a SQL window partition instead of take 2000. Only drop unattributed windows when a fresher attributed reading exists (provider-scoped). Enforce legacy/producer id collisions with suffix re-key. Co-authored-by: Jay Wedgeworth <jaywedgeworth22@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
|
Public API coverage gap: Kody rule violation: Every exported schema or utility ships with tests and must typecheck |
|
Renderer-unsafe sentence spacing in the PR description prevents the required two-sentence spacing from surviving rendering. Separate the two sentences with the renderer-safe Kody rule violation: Use two spaces between sentences in every human-facing string and agent-written paragraph |
Keep this PR's machine-provenance effort-log row and take main's 2026-10-05 entries. Auto-merged muse into the quota-windows provider grouping test.
Bare catch {} swallowed $queryRaw errors and dropped to the 400-row
findMany with no log. Capture the exception in Sentry (guarded so
observability never blocks the fallback) and console.error the same
failure.
Co-authored-by: Jay Wedgeworth <jaywedgeworth22@users.noreply.github.com>
Co-authored-by: Jay Wedgeworth <jaywedgeworth22@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
Loader returns quota events newest-first; reserving legacy ids in a separate pass keeps attributed collision re-keys correct regardless of input order. Regression test now covers both orderings. Co-authored-by: Jay Wedgeworth <jaywedgeworth22@users.noreply.github.com>
Code Review Could Not Complete
|
| Options | Enabled |
|---|---|
| Bug | ✅ |
| Performance | ✅ |
| Security | ✅ |
| Business Logic | ✅ |
| }, | ||
| })); | ||
|
|
||
| vi.mock("@sentry/nextjs", () => ({ |
There was a problem hiding this comment.
The vi.mock call for @sentry/nextjs adds Sentry to the test module graph, violating Rule 94’s requirement that Datadog remain the sole observability backend. Refactor the loader and test to use and mock the project’s Datadog-backed observability abstraction instead.
Also found in:
src/lib/quota-events-loader.ts:2-2src/lib/quota-events-loader.ts:83-83
Kody rule violation: Never expose secrets or private infrastructure values; reuse existing fleet env vars
Prompt for LLM
File src/lib/__tests__/quota-events-loader.test.ts:
Line 18:
The `vi.mock` call for `@sentry/nextjs` adds Sentry to the test module graph, violating Rule 94’s requirement that Datadog remain the sole observability backend. Refactor the loader and test to use and mock the project’s Datadog-backed observability abstraction instead.
**Also found in:**
- `src/lib/quota-events-loader.ts:2-2`
- `src/lib/quota-events-loader.ts:83-83`
Talk to Kody by mentioning @kody
Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.
Summary
producerInstanceIdand an optional human-readablemachinelabel when supplied.Open Review Findings
_producerInstanceIdand another does not.skipModelTypesis aggregated across all machines, so a stale or exhausted Antigravity window on one machine can suppress that model fleet-wide.Closes #1594