Predictalytics

T

RichardandClaude Fable 5 940a99fec2 Retry analytics on concurrent-modification conflicts instead of erroring

The reconciliation worker resets position checkpoints via bulk UPDATE while
the analytics worker saves recalculated positions for the same trader —
MySQL then rejects the stale save ("Record has changed since last read").
The engine run is now retried once with a fresh context (re-reading the
concurrent change); if it still collides, it logs a warning and lets the
next cycle pick the trader up again (LastAnalyzedAt stays unset).

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

2026-07-10 18:48:51 +02:00

Spike

feat: Implement copytrading analytics and update WebUI

2026-07-06 11:55:38 +02:00

src

Retry analytics on concurrent-modification conflicts instead of erroring

2026-07-10 18:48:51 +02:00

.gitignore

Initial commit: Predictalytics solution

2026-07-01 19:53:29 +02:00

Directory.Build.props

Initial commit: Predictalytics solution