Skip to content

fix(logs): apply filter predicates to merged in-memory call-log rows - #11082

Merged
diegosouzapw merged 1 commit into
cheaper-inference:release/v3.8.50from
AndrianBalanescu:fix/call-logs-row-filter
Aug 22, 2026
Merged

diegosouzapw merged 1 commit into
cheaper-inference:release/v3.8.50from
AndrianBalanescu:fix/call-logs-row-filter

Conversation

@AndrianBalanescu

Copy link
Copy Markdown
Contributor

Summary

  • getCallLogs() filters persisted database rows server-side, but in-memory rows (in-flight active requests and recently completed items from the runtime buffer) are merged in via buildCallLogListRows().
  • Previously, only correlationId was filtered after merging, allowing active/completed in-memory rows to bypass filters like search, model, provider, account, apiKey, status, and combo.
  • Adds rowMatchesFilter() over the merged result set, correctly filtering in-memory items while preserving DB results idempotently.
  • Adds regression unit tests for all predicate conditions in tests/unit/call-logs-row-filter.test.ts.

Testing

  • node --import tsx/esm --test tests/unit/call-logs-row-filter.test.ts passes (4/4).
  • ESLint checks clean for changed files.

@diegosouzapw
diegosouzapw merged commit 80d931a into cheaper-inference:release/v3.8.50 Aug 22, 2026
9 of 16 checks passed
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…heaper-inference#11082)

Validated on a combined board over tip c2d6247 (incl. sibling cheaper-inference#11081): call-logs-row-filter 4/4 green, typecheck:core clean. The merged-row predicate fix closes a real gap — in-memory (in-flight/recently-completed) rows bypassed every filter except correlationId; rowMatchesFilter() now applies search/model/provider/account/apiKey/status/combo uniformly while DB rows stay idempotent. Thank you @AndrianBalanescu!
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.

2 participants