Skip to content

fix: remove 500-row cap that truncated viewer count displays#1954

Open
chiefmojo wants to merge 1 commit into
MemTensor:dev-20260604-v2.0.19from
chiefmojo:fix/viewer-count-cap
Open

fix: remove 500-row cap that truncated viewer count displays#1954
chiefmojo wants to merge 1 commit into
MemTensor:dev-20260604-v2.0.19from
chiefmojo:fix/viewer-count-cap

Conversation

@chiefmojo

Copy link
Copy Markdown

Problem

clampLimit() in _helpers.ts hard-caps query limits at 500 rows. The viewer's trace and episode count displays fetch the first N rows to count totals, so any store with more than 500 items shows a truncated count.

Fix

Raise the cap from 500 to 100,000. This is a safety guard against pathological inputs, not a query-size policy — reasonable operators setting limit: 10_000 for bulk exports should not be silently truncated.

export function clampLimit(n: number): number {
  if (!Number.isFinite(n) || n <= 0) return 50;
  return Math.min(Math.trunc(n), 100_000);
}

clampLimit() in _helpers.ts capped all repo list() calls at 500,
silently truncating skill/policy/world-model counts everywhere they
were derived from array length rather than a COUNT(*) query.

- Raise clampLimit cap 500 → 100,000 so metrics() and other internal
  analytics can read full datasets (fixes Analytics tab)
- Rewrite /api/v1/overview to use countSkills/countPolicies/
  countWorldModels/countEpisodes instead of list+length, making
  Overview counts correct regardless of scale (fixes Overview tab)
- Align countSkills to use limit:100_000 consistent with other
  count methods
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