Turso sync#45
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (8)
📒 Files selected for processing (11)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add `features = ["sync"]` to the turso Cargo dependency so the turso::sync module is available at compile time. Co-authored-by: SCE <sce@crocoder.dev>
…stants These `pub(crate)` constants follow the established pattern from observability env keys (LOG_LEVEL_ENV_KEY, etc.) and are the configuration seam for dual-mode TursoDb initialization. Co-authored-by: SCE <sce@crocoder.dev>
Extend TursoDb<M> to support Turso Cloud sync mode via turso::sync::Builder::new_remote() when both SCE_SYNC_URL and SCE_SYNC_TOKEN are set. Sync-mode methods (push/pull/checkpoint/stats) are explicit — no auto-push from execute(). Wire a user-invocable sce sync push|pull CLI command behind the new sync module (cli/src/services/sync/), connected through clap schema, command registry, and parse runtime dispatch. Remove the unused SYNC_PUSH_THRESHOLD_ENV_KEY constant and write-counter auto-push approach from the earlier design. Co-authored-by: SCE <sce@crocoder.dev>
AgentTraceDbLifecycle::setup now captures the AgentTraceDb::new() result and performs an initial pull() when sync mode is active (both SCE_SYNC_URL and SCE_SYNC_TOKEN set). The pull is best-effort — remote failure is logged via tracing::warn! and setup continues without error. Co-authored-by: SCE <sce@crocoder.dev>
Allow database specs to opt in to Turso Cloud sync and enable it for the Agent Trace DB. Disable empty remote bootstrapping for sync connections and use non-AUTOINCREMENT integer primary keys for compatibility with synced trace tables. Co-authored-by: SCE <sce@crocoder.dev>
No description provided.