Skip to content
Source
Sign inSign up
TanStack/schemas

Replicate run counts write a model.updated event on every poll #92

Send to my agent
Closedtombeckenham opened this issue 0 comments
tombeckenhamcommented

Problem

GET /v1/changes?provider=replicate is a stream of model.updated events whose only delta is capabilities.runCount.

toModelInfo in src/server/providers/adapters/replicate.ts stores Replicate's run_count on the model:

capabilities: {
  visibility: model.visibility,
  runCount: model.run_count,
  official: model.is_official,
}

The 15-minute model poll diffs the whole capabilities object. A count moving from 26026 to 26039 writes "Model krea/krea-2-large updated". One poll at createdAt 1790748994 produced a full page of these. The catalog has 552 Replicate models, and popular ones tick on almost every poll.

visibility and official are stable. The run count is usage telemetry, not a catalog change.

Impact

Subscribers and /v1/changes consumers cannot tell a real Replicate model change from a counter tick. Replicate dominates the change feed.

Ask

Stop persisting runCount on Replicate models so a run-count change does not write model.updated.

Keep visibility and official.

Acceptance

  • A poll where only run_count changed writes no model.updated row.
  • A poll that changes visibility or official still writes model.updated.
  • New and existing Replicate model rows do not store runCount.
  1. tombeckenham closed this

Sign in to join this conversation.