Skip to content

fix: skip stale signal_triage rows instead of re-inserting during sna…#33

Open
JW-90124 wants to merge 1 commit into
barretlee:mainfrom
JW-90124:fix/snapshot-restore-stale-triage
Open

fix: skip stale signal_triage rows instead of re-inserting during sna…#33
JW-90124 wants to merge 1 commit into
barretlee:mainfrom
JW-90124:fix/snapshot-restore-stale-triage

Conversation

@JW-90124

@JW-90124 JW-90124 commented Jul 20, 2026

Copy link
Copy Markdown

…pshot restore

When a snapshot row is older than the existing database row, the previous logic fell through to the insert branch and violated the signal_triage primary key. Stale rows are now skipped.

Summary

Verification

  • npm run check
  • No secrets, private data, databases or raw payloads are included
  • Source licensing and access boundaries were reviewed (if applicable)
  • Docs/specs were updated for workflow, schema or ranking changes

…pshot restore

When a snapshot row is older than the existing database row, the previous
logic fell through to the insert branch and violated the signal_triage
primary key. Stale rows are now skipped.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@JW-90124

Copy link
Copy Markdown
Author

Note on CI: the failures in tests/scout.test.ts and tests/integration.test.ts
are unrelated to this PR. They are caused by hardcoded dates in the test fixtures
expiring naturally — e.g. expires_at: "2026-07-20T00:00:00.000Z" at
scout.test.ts:168 — so they reproduce on main as well from 2026-07-20 onward.

Separately, I noticed the scheduled "Refresh intelligence data" workflow on this
repository has been failing for the past two days. The symptom matches the
signal_triage primary-key violation this PR fixes, in case that's helpful.

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