TRCKR-835 - trckr

← TRCKR-835

bug cli

Created: 2026-01-03 • Updated: 2026-01-03

Relationships Loading...

## Bug Description

When a client runs `trckr sync configure` for the first time, it starts tracking from the current server version without pulling historical data. This means the client has an empty local database despite the server having thousands of issues.

## Current Behavior

1. User runs `trckr sync configure --server-url ... --api-key ...`
2. Client records the current server version (e.g., 13000+)
3. Running `trckr sync` only pulls incremental changes since version 13000
4. Local database shows 0 projects and ~5 issues while server has 8000+ issues

## Expected Behavior

On first configure (or when `last_sync_version = 0`), the sync should automatically:
1. Detect this is a fresh client
2. Pull the latest snapshot from the server
3. Apply all snapshot data to local database
4. Then continue with incremental sync

## Workaround

Currently users must manually run:
```bash
trckr sync reset --yes
trckr sync
```

This resets `last_sync_version` to 0, which triggers the fresh client logic and pulls the full snapshot.

## Impact

- New users see empty issue lists after configuring sync
- Causes confusion and support requests
- Easy to miss that data isn't syncing

## Suggested Fix

In `client/sync.py`, after `sync configure` succeeds, automatically trigger a full sync with `is_fresh_client=True` or set `last_sync_version=0` to ensure snapshot download.

Pull Requests (comma-separated URLs)

Attachments

Comments (1)

agent · 2026-01-03

## Fix Applied **Root Cause:** The `sync configure` command saved the sync configuration but did not trigger an initial sync. Since `last_sync_version` is initialized to 0 for new clients, the first `sync()` call would correctly pull a full snapshot - but users had to manually run `trckr sync` after `sync configure`. **Changes Made:** 1. **trckr.py:425-475** - Modified `sync_configure` command to: - Automatically trigger `engine.sync()` after configuration succeeds - Handle sync errors gracefully (AuthError, NetworkError, SyncError) - Added `--no-sync` flag to skip initial sync when not needed - Display progress: "Performing initial sync..." and "Downloaded N entities" 2. **tests/test_sync_cli.py** - Updated tests: - Added `--no-sync` to tests that don't need network calls - Added new test `test_configure_triggers_initial_sync` to verify sync is attempted - Updated 4 existing tests to use `--no-sync` flag **Verification:** - All 10 sync CLI tests pass - Initial sync triggers automatically after configure - Network/auth errors are handled gracefully with helpful retry messages **Usage:** ```bash # New behavior - full sync happens automatically trckr sync configure --server-url https://trckr.example.com --api-key sk-xxx # Skip initial sync if needed trckr sync configure --server-url https://trckr.example.com --api-key sk-xxx --no-sync ```